Project

Profile

Help

Issue #8260

closed

Use get_user_model instead of auth.models.user

Added by ipanova@redhat.com about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
GalaxyNG
Sprint:
Sprint 90
Quarter:

Description

mporting and using django.contrib.auth.models.User breaks any apps that use custom user models defined in AUTH_USER_MODEL. To prevent this from happening, the User model should be loaded using django's get_user_model() function.

See https://docs.djangoproject.com/en/3.1/topics/auth/customizing/#referencing-the-user-model for details

Actions #1

Updated by ipanova@redhat.com about 3 years ago

  • Sprint/Milestone set to 2.3.1

Added by newswangerd about 3 years ago

Revision 0aaeef4e | View on GitHub

Use get_user_model instead of auth.models.user

closes #8260

Added by newswangerd about 3 years ago

Revision 0aaeef4e | View on GitHub

Use get_user_model instead of auth.models.user

closes #8260

Actions #3

Updated by newswangerd about 3 years ago

  • Status changed from NEW to MODIFIED

Added by newswangerd about 3 years ago

Revision cb3302de | View on GitHub

Use get_user_model instead of auth.models.user

closes #8260

(cherry picked from commit 0aaeef4e535170b38d81a644ad56a2a86dd7e7fd)

Added by newswangerd about 3 years ago

Revision cb3302de | View on GitHub

Use get_user_model instead of auth.models.user

closes #8260

(cherry picked from commit 0aaeef4e535170b38d81a644ad56a2a86dd7e7fd)

Actions #5

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions #6

Updated by ipanova@redhat.com about 3 years ago

  • Tags GalaxyNG added
Actions #7

Updated by ipanova@redhat.com about 3 years ago

  • Sprint set to Sprint 90

Also available in: Atom PDF