Project

General

Profile

Actions
Copy link

Idea #13255

closed

Provide account activation configuration options for federated logins

Added by Tom Morris over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Peter Amstutz
Category:
-
Target version:
2018-07-03 Sprint
Start date:
06/21/2018
Due date:
Story points:
2.0
Release:
Arvados 1.2
Release relationship:
Auto

Description

Currently, a user who authenticates for the first time to a "local" cluster using their existing account at a "remote" cluster (their "home" cluster) is automatically activated if
  • Their account is active at their "home" cluster, and
  • "Auto-activate new users" is enabled on the local cluster.

Otherwise, the user lands in an inactive account.

Options:
  • auto activate federated remote accounts
  • allow specific approval and activation of remote accounts (??? does this mean current behavior?)

Proposed behaviors

  • Auto activate: list of cluster ids for which it honors the "is_active" flag (current behavior is to ignore the is_active flag and use the local cluster's autoactivate policy)

Subtasks 2 (0 open — 2 closed)

Task #13659: Review 13255-account-activationResolvedPeter Amstutz06/22/2018Actions
Task #13672: document account activationResolvedPeter Amstutz06/21/2018Actions

Related issues

Related to Arvados - Feature #12958: [Federation] Workbench login chooserClosedActions
Related to Arvados - Bug #13020: Login into workbench with a salted token activates a previously inactive federated accountDuplicateLucas Di Pentima10/30/2019Actions
Actions
Copy link

Also available in: Atom PDF