-
Notifications
You must be signed in to change notification settings - Fork 28
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
Social auth layer #107
Comments
I'm starting to work on this. |
Hey @shaib how are things going on this? |
@shaib made some progress on this feature, but various parts of the project API changed during that time. Whoever picks up this task could look at Shai's work here: https://github.com/shaib/openbudgets/tree/hackathon and pick up from there. |
Done, now only missing a nice design, and a fix to the account_details view that sometimes only gets updated after another full page refresh after disconnecting from one of the networks or adding another one |
We're currently working on a new design for the whole project, so we'll wait before we implement the design for this. |
Still, in order for it to be functional, it needs a more reasonable design, we should probably close this issue, and open another issue for the design of the social auth buttons, and assign it to me, once it'll be done, we can finally merge it. |
We want to add the ability to login via Facebook, Twitter, and Google+ to Open Muni.
This social auth layer must be completely transparent and integrated with the "native" auth that is already in place.
For all social auth, we want to access the user email (so the oauth scope needs to reflect that), and also First Name + Last Name if available on the service.
Services that allow us to post data via the user (fb and twitter), must get this permission too, as part of the auth process.
Any implementation must work with existing users, not just new users. We must support use cases where:
We'd like this implemented with django-social-auth:
If you have a suggestion you think is better, please make a case for it here, in the comments.
And, specifically on the issue of native auth combined with a number of social auths, you can refer to this thread in the django-social-auth mailing list:
https://groups.google.com/forum/?fromgroups#!topic/django-social-auth/YvijRk3QhSY
If any of the requirements are unclear, please ask @pwalsh or @ydaniv before starting to code.
Here are our docs, on accounts in Open Muni, as they exist currently:
http://open-budget.readthedocs.org/en/latest/guide/features/accounts.html
The text was updated successfully, but these errors were encountered: