Project

Profile

Help

Task #1874

closed

Plan User/Auth system for 3.0

Added by mhrivnak almost 8 years ago. Updated about 5 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

The user/auth system in 2.y has many opportunities for improvement. Porting it from mongodb to postgres might take about the same effort as standardizing on django's auth.

There are many advantages to using django's auth, including having less custom code, and being able to easily use complimentary apps like django-admin.

https://docs.djangoproject.com/es/1.9/topics/auth/

This task is to investigate django's auth, whether it meets our needs (it may need to be extended for path-based authz), and how it would affect current use cases. As a bonus, investigate how it could integrate with freeipa.


Related issues

Related to Pulp - Task #1803: Plan replacement of mongodb with postgresCLOSED - CURRENTRELEASEsemyers

Actions
Related to Pulp - Task #1873: Plan REST API for 3.0CLOSED - CURRENTRELEASEsemyers

Actions
Is duplicate of Pulp - Task #2090: Create a plan for user/auth in 3.0CLOSED - CURRENTRELEASEttereshc

Actions

Also available in: Atom PDF