Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #4077

closed

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

Added by bmbouter over 5 years ago. Updated over 4 years 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:
No
Sprint Candidate:
No
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)

Actions
Copy link
 #1

Updated by bmbouter over 5 years ago

This is blocking the integration with galaxy.ansible.com

Actions
Copy link
 #2

Updated by bmbouter over 5 years ago

I posted a possible fix in this PR here: https://github.com/pulp/pulp/pull/3711/files

Actions
Copy link
 #3

Updated by bmbouter over 5 years ago

  • Status changed from NEW to POST
Actions
Copy link
 #4

Updated by bmbouter over 5 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #5

Updated by bmbouter over 5 years ago

  • Status changed from MODIFIED to POST

Moving to post to attach another issue

Actions
Copy link
 #6

Updated by CodeHeeler over 5 years ago

  • Triaged changed from No to Yes

Added by Alexander Saprykin over 5 years ago

Revision b2471634 | View on GitHub

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

Added by Alexander Saprykin over 5 years ago

Revision b2471634 | View on GitHub

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

Actions
Copy link
 #7

Updated by Anonymous over 5 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #8

Updated by daviddavis about 5 years ago

  • Sprint/Milestone set to 3.0.0
Actions
Copy link
 #9

Updated by bmbouter almost 5 years ago

  • Tags deleted (Pulp 3)
Actions
Copy link
 #10

Updated by bmbouter over 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF