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

oauth #804

Closed
markherringer opened this issue Jun 15, 2016 · 2 comments
Closed

oauth #804

markherringer opened this issue Jun 15, 2016 · 2 comments

Comments

@markherringer
Copy link
Member

markherringer commented Jun 15, 2016

as a user I want to sign in with my social media account so that I can access healthsites easily

osm -
Github -
linkedin -
google -
twitter - done
facebook - done

during the sign on process I expect to be informed of the data healthsites will use from my account and how I can manage it.

@dodobas
Copy link
Contributor

dodobas commented May 14, 2017

so we are missing support for osm, linkedin and google oauth providers? and we should enable those?

@markherringer
Copy link
Member Author

We need to review how we want this process to work...

The OSM account will be the primary account.
It will will allow the user to write directly to OSM once #888 and #889 have been developed.

The idea of having the Twitter, Facebook and Linkedin accounts available achieve the following two objectives:

  1. Easy authentication
  2. Opportunities to share Healthsite locations into Social networks and request validations

They should be seen as secondary to the OSM account.

From the profile page, established following the initial registration, the user can choose to add additional profiles to the account.
https://healthsites.io/profile/sharehealthdata/

When a user wants to share a healthsite with Twitter/Facebook/Linkedin the system should detect which authentication method is active and either proceed or redirect back to profile/page and request activation.

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

No branches or pull requests

4 participants