D
D
dizlv2015-10-30 22:52:39
Django
dizlv, 2015-10-30 22:52:39

How to make a single login/registration service for different modules of the same project?

Django project. At the moment login/registration is done through standard Django's tools.
The task is to make a single login for the Web interface (not rest api), mobile applications, and so on.
Those. in my understanding, it should look something like this:
login form - we log in through anything, for everything we use one interface, the implementation of which will decide where to send the request next - social network, our own database, etc., we get a session / token and we are working on this further.
I looked in the direction of oauth2, but I do not quite understand how to implement it.
Maybe someone faced similar problems? What to do?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
N
Nikolai Korabelnikov, 2015-11-05
@nmk2002

I recommend considering SAML. When trying to open a web resource for the first time, the user will receive a redirect to the Identity Provider, that is, to the authentication server. He will offer to authenticate and then redirect the user with an access token back to the resource. For the following resources, redirects will be made without the need for re-authentication.
OAuth2 is also an option, although initially it is an authorization standard, that is, granting rights. But you can indirectly authenticate the user. For this option, you also need an authentication server that supports this standard.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question