SSO: Auth0 integration #355
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ababic
force-pushed
the
auth0-integration
branch
2 times, most recently
from
32b8c10
to
86c70ce
Compare
ababic
force-pushed
the
auth0-integration
branch
4 times, most recently
from
3951e2b
to
828b5d8
Compare
ababic
force-pushed
the
auth0-integration
branch
from
a9a5b8f
to
67b540b
Compare
ababic
force-pushed
the
auth0-integration
branch
8 times, most recently
from
32e9410
to
5b62fd0
Compare
ababic
commented
Jul 1, 2022
ababic
force-pushed
the
auth0-integration
branch
3 times, most recently
from
9c3496a
to
dbcfe2c
Compare
ababic
force-pushed
the
auth0-integration
branch
from
dbcfe2c
to
00b1736
Compare
ahosgood
added
the
chore
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds basic integration with Auth0, allowing users from the connected Auth0 tenant to authenticate using the Auth0 login page.
If the user HASN'T authenticated with the app before, successful authentication results in the creation of a basic Django user with an unusable password
*and no special privileges. This user then becomes the active user for the remainder of the app session.If the user HAS authenticated with the app before, successful authentication results in the existing Django user being found (via a linked
IDPProfileobject with a matchingprovider_user_idvalue), and becoming the active user for the remainder of the app session*Setting an 'unusable password' in Django prevents the user from logging in via Django's regular email/password mechanisms, and also prevents them from initialising a password reset from Django - meaning they can only authenticate via Auth0.