Bug #3465
closed
- Target version set to Arvados Future Sprints
- Subject changed from [Docker] upgrade SSO codebase to use oauth2 (or openid connect) and migrate auth.curoverse.com to [Docker] upgrade SSO codebase to use oauth2 (or openid connect)
The SSO server uses openid to authenticate with Google. Internally, it uses oauth2 to talk to the Arvados services.
Google is phasing out openid support, cf. https://developers.google.com/accounts/docs/OpenID.
The reason we used openid to authenticate with Google, is that it requires no Google token or account for the SSO server. This makes deployment easier.
- Target version changed from Arvados Future Sprints to 2014-11-19 sprint
- Subject changed from [Docker] upgrade SSO codebase to use oauth2 (or openid connect) to [SSO] upgrade SSO codebase to use oauth2 (or openid connect)
- Assigned To set to Peter Amstutz
- Description updated (diff)
- Story points changed from 2.0 to 5.0
- Story points changed from 5.0 to 3.0
- Subject changed from [SSO] upgrade SSO codebase to use oauth2 (or openid connect) to [SSO] Research requirements to upgrade SSO codebase to use oauth2 (or openid connect)
- Status changed from New to Resolved
- Status changed from Resolved to New
- Status changed from New to Resolved
Also available in: Atom
PDF