Story #15107

[controller] Implement native Google login (configurable as an alternative to sso-provider)

Added by Tom Clegg 3 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
3.0

Description

See Native login implementation

Implement an OpenID Connect login mechanism that supports (at least) Google login.

Cluster configuration should make it possible to
  • continue using sso-provider as before (default), or
  • use the new OpenID Connect mechanism to sign in with Google.
This issue does not include:
  • Offering the user a backend chooser
  • Supporting both sso-provider and OpenID Connect at the same time
  • Supporting multiple backends at the same time
  • LDAP

Related issues

Blocks Arvados - Story #15322: [Epic] Replace and delete sso-providerNew

History

#1 Updated by Tom Clegg 3 months ago

  • Subject changed from [controller] Implement native login (to replace sso-provider) to [controller] Implement native Google login (configurable as an alternative to sso-provider)
  • Description updated (diff)
  • Category set to API
  • Story points set to 3.0

#2 Updated by Tom Morris 3 months ago

  • Target version changed from To Be Groomed to Arvados Future Sprints

#3 Updated by Tom Clegg about 2 months ago

  • Blocks Story #15322: [Epic] Replace and delete sso-provider added

#4 Updated by Tom Clegg about 2 months ago

  • Target version changed from Arvados Future Sprints to 2019-06-19 Sprint
  • Assigned To set to Tom Clegg

#5 Updated by Tom Clegg about 2 months ago

  • Target version changed from 2019-06-19 Sprint to Arvados Future Sprints
  • Assigned To deleted (Tom Clegg)

Also available in: Atom PDF