Project

General

Profile

Actions

Feature #12958

closed

[Federation] Workbench login chooser

Added by Tom Clegg almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Story points:
-
Release relationship:
Auto

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.

When the user selects a remote cluster, the login URL should include the current cluster ID as the "remote" query parameter, which tells the login cluster to issue a salted token for the current cluster. See #14718.

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.

If a user logs in to an identity_url that corresponds to a remote user, or has a redirect_to_user_uuid to a remote user, results in a browser redirect to the user's home cluster for federated login.

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 - Idea #11454: Support federated search across a set of Arvados clustersResolvedLucas Di Pentima04/11/2017Actions
Related to Arvados - Idea #13255: Provide account activation configuration options for federated loginsResolvedPeter Amstutz06/21/2018Actions
Related to Arvados - Feature #14720: [Federation] Workbench2 login chooserResolvedPeter Amstutz02/13/2019Actions
Blocked by Arvados - Feature #14718: [API] Option to issue salted token in login procedureResolvedLucas Di Pentima01/26/2019Actions
Actions

Also available in: Atom PDF