Task #5789


Some issues to be cleared about userservice

Added by Marcus Przyklink over 5 years ago. Updated over 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
PM Check date:


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

Related issues 1 (0 open1 closed)

Related to Open Infrastructure - Task #6465: Expire the password reset link [datacenterlight, dynamicweb]RejectedMondi Ravi02/15/2019

Actions #1

Updated by Nico Schottelius over 5 years ago

  • Assignee changed from Nico Schottelius to Marcus Przyklink

I suggest the following development flow:

  • create a new project, based on latest (stable) django
    • Using micro services should give us the opportunity to easily use different versions
  • in this project users should be able to
    • register a new user account
    • login
    • reset their password
    • register & login should have some kind of logic that allows our main website to refer to it ("secured area") and get back to it
    • I assume the last part can/should be done using oauth(2)
  • Change dynamiweb to use the new user service
    • consult with Mondi here - he might actually be good to do it && show you what changes were needed
  • Later stage
    • publish events on the message bus (user registered, user password reset, etc.)
Actions #2

Updated by Jason Kim over 5 years ago

  • PM Check date set to 02/05/2019
Actions #3

Updated by Mondi Ravi over 5 years ago

  • Related to Task #6465: Expire the password reset link [datacenterlight, dynamicweb] added
Actions #4

Updated by Sanghee Kim about 5 years ago

  • Project changed from 15 to queue
  • Status changed from Feedback to New
  • Assignee deleted (Marcus Przyklink)
Actions #5

Updated by Nico Schottelius over 1 year ago

  • Status changed from New to Rejected

Also available in: Atom PDF