Feature #13651

Ability to merge a local account into a remote (federated) account

Added by Peter Amstutz 6 months ago. Updated 6 months ago.

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

0%

Estimated time:
Story points:
-

Description

We have the ability in the API server and workbench to migrate users, this means means reassigning ownership of objects from one user to another, and redirecting one local user login to another.

For federation, we will want to extend this feature to be able to migrate a local user account to a federated identity (a "remote" user). This means:

  • Everything owned by the "local" user is reassigned to the remote user
  • One of:
    • logging in as the local user actually logs in (for that cluster only) as the remote user.
    • OR logging in with the local account is deactivated and only federated login is possible
  • API server "user merge" feature needs to work when one of the users are a remote user
  • May depend on additional login flow for federated logins (#12958)

Related issues

Related to Arvados - Feature #12958: [Federation] Workbench login chooserNew

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

History

#1 Updated by Peter Amstutz 6 months ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 6 months ago

  • Related to Feature #12958: [Federation] Workbench login chooser added

#3 Updated by Peter Amstutz 6 months ago

  • Description updated (diff)
  • Status changed from In Progress to New

#4 Updated by Peter Amstutz 6 months ago

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

#5 Updated by Lucas Di Pentima 6 months ago

Reviewing this ticket for grooming I didn't found any reason as for why this feature shouldn't already work.
Maybe this story is just about writing the tests that proves the feature work?

Also available in: Atom PDF