Actions
Task #5789
closedSome issues to be cleared about userservice
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/09/2018
Due date:
% Done:
0%
Estimated time:
PM Check date:
02/05/2019
Description
Some issues which should be cleared:
- django update. If we wanna use ldap, I think we should use django-auth-ldap as an auth backend. For that, we would need django >=1.11. I seem to remember reading about an update, but can't seem to find where it was. Is that in the making in the foreseeable future?
- 'should use ldap' -> I presume it means ldap first, old db as fallback?
- We should develop some concept for a fast and easy migration of the old database into ldap at some point, else we will need two bunches of code to handle everything
- Since django-auth-ldap uses the django-db for storing, we would have two sets of data there, the old customerset and the new one the ldap-auth puts there, so I will see if it is easily identifyable what is what
- another thing.. This is more customer relations. Everyone already in the db will need new passwords if we migrate to ldap, which is a hassle and should be thought about by marketing to give it a good spin
Maybe the scope is a bit broad, but those are the things which popped into my mind while thinking about how to best integrate the userservice
Actions