Actions
Bug #16989
closedWorkbench1 user is setup on home cluster but not setup on satellite cluster
Story points:
-
Release:
Release relationship:
Auto
Description
- Have a LoginCluster and a satellite cluster. Both clusters are set AutoSetupUsers: true
- New user appears on satellite cluster, logs in, and account is created
- User is set up on LoginCluster, is_invited=true, is_active=false
- Being inactive, the user is un-setup on the satellite cluster which makes them un-invited
- Workbench has the user as is_invited=false (?) which sends them to the inactive user page
- Why isn't the user record is_active=true ?
- Going to Workbench 2 (which always tries to self-activate) the user does get activated. However, no welcome email is sent out.
Possibly related: on pirca, go to user page, click on "Set up user", the dialog box opens for a second and then immediately goes away.
It's possible to activate the user at the command line, and with --send-notification-email an email does go out.
Desired behavior:
User arrives at the satellite cluster. Login happens transparently through the LoginCluster and user is returned to the satellite workbench. User is auto-setup and gets welcome email from satellite.
Related issues
Updated by Peter Amstutz about 4 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz about 4 years ago
16989-user-setup @ arvados|2958a94fafbab941f8d6eb76bb2785b5c2868d3d
- Rework how remote user setup/activate/unsetup state is synchronized
- Sending welcome email is moved to model
- Add test for all combinations of user status and relevant configuration.
Updated by Peter Amstutz about 4 years ago
- Blocks Idea #16662: Release Arvados 2.1 added
Updated by Peter Amstutz about 4 years ago
- Status changed from In Progress to Resolved
Actions