Issue #4077: pulpcore can't be installed in a Django site that also ships a a custom User object - Pulp

Send by e-mail

Issue #4077

pulpcore can't be installed in a Django site that also ships a a custom User object

Added by bmbouter over 2 years ago. Updated about 1 year ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

Problem¶

The pulpcore app isn't "reusable" because of this. See https://docs.djangoproject.com/en/2.1/topics/auth/customizing/#reusable-apps-and-auth-user-model

Solution¶

I'm not sure of all the implications but we could:

(a) stop shipping a custom user model entirely.
(b) move the user bits to their own python package
(c) find an existing Django app that users can install/configure that is effectively solution (b)

Associated revisions

Revision aa519c8e View on GitHub
Added by bmbouter over 2 years ago

Removes custom User model

https://pulp.plan.io/issues/4077 closes #4077

Revision aa519c8e View on GitHub
Added by bmbouter over 2 years ago

Removes custom User model

https://pulp.plan.io/issues/4077 closes #4077

Revision b2471634 View on GitHub
Added by Alexander Saprykin about 2 years ago

Fix user serializer for custom user model

In case of custom user model used, PasswordSerializer fails because it relies on builtin into Django user model. This patch add dynamic user model resolving.

closes #4077

Revision b2471634 View on GitHub
Added by Alexander Saprykin about 2 years ago

Fix user serializer for custom user model

In case of custom user model used, PasswordSerializer fails because it relies on builtin into Django user model. This patch add dynamic user model resolving.

closes #4077