Skip to content
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

Open
CuriousLearner opened this issue Jan 9, 2017 · 5 comments
Open

Using SSO for all users #5

CuriousLearner opened this issue Jan 9, 2017 · 5 comments

Comments

@CuriousLearner
Copy link
Contributor

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.

@aktech
Copy link
Contributor

aktech commented Jan 9, 2017

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.

@CuriousLearner
Copy link
Contributor Author

CuriousLearner commented Jan 9, 2017

I'm just referring to Authentication here. Authorization would still be using the Permission class as discussed. Makes sense?

@aktech
Copy link
Contributor

aktech commented Jan 10, 2017

According to wiki definition:

With this property a user logs in with a single ID and password to gain access to a connected system or systems without using different usernames or passwords, or in some configurations seamlessly sign on at each system.

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.

@CuriousLearner
Copy link
Contributor Author

CuriousLearner commented Jan 11, 2017

What I have in my mind is this scenario:

User just enter their email address -- A unique login link is generated for them which is mailed to them.

They click on it and are authenticated.

Authorization would still be with Permissions. This is just Authentication. Makes sense?

@aktech
Copy link
Contributor

aktech commented Jan 11, 2017

Makes perfect sense. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants