Project

General

Profile

Actions
Copy link

Bug #3465

closed

[SSO] Research requirements to upgrade SSO codebase to use oauth2 (or openid connect)

Added by Ward Vandewege over 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Peter Amstutz
Category:
-
Target version:
2014-11-19 sprint
Story points:
3.0

Description

https://developers.google.com/accounts/docs/OAuth2Login

Subtasks 2 (0 open — 2 closed)

Task #4379: Talk to Ward about what this involvesResolvedPeter Amstutz11/05/2014Actions
Task #4429: Document authentication dance between Workbench, API, SSO and external identity providerResolvedPeter Amstutz11/05/2014Actions

Related issues 1 (0 open — 1 closed)

Related to Arvados - Feature #4570: [SSO] Implement Google OAuth2 for new SSO installationsResolvedPeter Amstutz11/05/2014Actions
Actions
Copy link
 #1

Updated by Tom Clegg over 10 years ago

  • Target version set to Arvados Future Sprints
Actions
Copy link
 #2

Updated by Ward Vandewege about 10 years ago

  • 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)
Actions
Copy link
 #3

Updated by Ward Vandewege about 10 years ago

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.

Actions
Copy link
 #4

Updated by Ward Vandewege about 10 years ago

  • Target version changed from Arvados Future Sprints to 2014-11-19 sprint
Actions
Copy link
 #5

Updated by Ward Vandewege about 10 years ago

  • Subject changed from [Docker] upgrade SSO codebase to use oauth2 (or openid connect) to [SSO] upgrade SSO codebase to use oauth2 (or openid connect)
Actions
Copy link
 #6

Updated by Ward Vandewege about 10 years ago

  • Assigned To set to Peter Amstutz
Actions
Copy link
 #7

Updated by Peter Amstutz about 10 years ago

  • Description updated (diff)
Actions
Copy link
 #8

Updated by Peter Amstutz about 10 years ago

  • Story points changed from 2.0 to 5.0
Actions
Copy link
 #9

Updated by Peter Amstutz about 10 years ago

  • Story points changed from 5.0 to 3.0
Actions
Copy link
 #10

Updated by Peter Amstutz about 10 years ago

  • 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)
Actions
Copy link
 #11

Updated by Peter Amstutz about 10 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #12

Updated by Peter Amstutz about 10 years ago

  • Status changed from Resolved to New

Workbench authentication process documented at Workbench authentication process

Actions
Copy link
 #13

Updated by Peter Amstutz about 10 years ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF