Additional OAuth providers about civic-server

[malachig]

I think we should start with these two. Quite a few of the early testers that we hope to get feedback from do not have a github account...

[malachig]

LinkedIn and Twitter would be great also.

[acoffman]

So, for Google OAuth, we'll need to set up a new application for civic on the google developer site. I can set this up with my own personal Google account, but that doesn't seem ideal. From the Google Analytics ticket, it sounds like both @malachig and @obigriffith have admin on the TGI organization account. Can one of you set up an app on that account by following the instructions here: https://github.com/zquestz/omniauth-google-oauth2#omniauth-google-oauth2-strategy. I went through most of the flow on my own account and its pretty simple.

Once its set up, then if you can send me the client id and client secret and I can incorporate it into CIVIC.

[acoffman]

(I don't expect that we'll be able to ship this today anyways, but before AGBT would be awesome!)

[malachig]

I think we were given view access in Google Analytics for the DGIdb application. I don't think we have admin on the TGI organization account though. Maybe @mcallaway can clarify this?

[malachig]

Here is a working list of ideas for OAuth providers:

• ORCid
• Google
• LinkedIn
• ResearchGate
• Twitter
• Yahoo

Unfortunately, it is likely that many clinicians will actually have none of these. Dr. Bose had the idea of using AACR, ASCO, ASH, ERA Commons, etc. membership somehow, but so far I see no evidence that any of these are OAuth providers. We should try to allow for several of these to cover as many people as possible and if they have none, to ask them to create a github account perhaps, and direct them to the right place to do that...

[acoffman]

I've just pushed an update that allows for logging in with Google and ORCid. We'll need to update the frontend to support this and decide the flow for credential collisions (two people with the same usernames on different sites, etc).