-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using SSO for all users #5
Comments
I think it would be very difficult in differentiating users of application by using SSO. I don't understand how would you manage authorization of different users, for e.g. a speaker and a volunteer will have different permissions. |
I'm just referring to |
According to wiki definition:
Perhaps, that we would be doing anyway for different systems like registration, talks management, email management, like a single login for each user for different systems, since we are extending Django AbstractUser, isn't it? Correct me if I am misinterpreting it. |
What I have in my mind is this scenario:
Authorization would still be with Permissions. This is just Authentication. Makes sense? |
Makes perfect sense. 👍 |
I was thinking to use SSO for all users (attendees, volunteers, speakers). This would actually help us to get rid of passwords + since we'll have email of all attendees, they can just login using SSO.
Let me know your thoughts on this.
The text was updated successfully, but these errors were encountered: