Feature #12958

[Federation] Workbench login chooser

Added by Tom Clegg 11 months ago. Updated 4 days ago.

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

0%

Estimated time:
Story points:
-

Description

If cluster B is configured to permit it, federated login allows an account on cluster A to use Workbench at cluster B. In that case, Workbench B should give an unauthenticated visitor the option to log in via cluster A.

Current behavior

An unauthenticated visitor to Workbench B is offered a "log in" button that initiates the login procedure for cluster B. If a cluster A user clicks it, they end up creating a new cluster B account, instead of using their existing cluster A account. After #11454 they can work around this by visiting Workbench A first and following a link from the multisite search page to Workbench B, but this is not obvious or convenient.

Proposed change

On a cluster with remote_hosts_via_dns enabled, the login button should come with a text box where the user can type a 5-letter cluster prefix.

On a cluster with specific remote_hosts defined, the login button should come with a selector widget so the user can choose one of the defined remotes.

If both configs are enabled, both widgets should be offered. If a user types an ID listed in remote_hosts, remote_hosts has precedence over remote_hosts_via_dns. Matching is case-insensitive.

If configured for a special "home" cluster, always redirect to the login endpoint of the "home" cluster, user will still be (eventually) returned to "remote" workbench. "Home" API server needs to know to send a salted token back to the remote workbench. This should also imply honoring the "is_active" flag.

Optional: Use LocalStorage to remember which cluster was chosen, and make that the default next time.

TBD

Visual/interactivity specifics. Note there is a big dialog-like login box, plus a login button in the top nav.


Related issues

Related to Arvados - Story #11454: Support federated search across a set of Arvados clustersResolved2017-04-11

Related to Arvados - Story #13255: Provide account activation configuration options for federated loginsResolved2018-06-21

Related to Arvados - Feature #13651: Ability to merge a local account into a remote (federated) accountNew

History

#1 Updated by Tom Morris 9 months ago

  • Related to Story #11454: Support federated search across a set of Arvados clusters added

#2 Updated by Tom Clegg 9 months ago

  • Related to Story #13255: Provide account activation configuration options for federated logins added

#3 Updated by Peter Amstutz 8 months ago

  • Description updated (diff)

#4 Updated by Peter Amstutz 6 months ago

  • Related to Feature #13651: Ability to merge a local account into a remote (federated) account added

Also available in: Atom PDF