Actions
Bug #18183
closed
Investigate the need for token revocation when deactivating a user account
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Story points:
-
Release:
Release relationship:
Auto
Updated by Peter Amstutz almost 3 years ago
- Target version changed from 2021-10-13 sprint to 2021-10-27 sprint
Updated by Peter Amstutz almost 3 years ago
- Target version changed from 2021-10-27 sprint to 2021-11-10 sprint
Updated by Ward Vandewege almost 3 years ago
- Status changed from New to In Progress
deactivating a user (in workbench1) results in an 'unsetup' api call on the user object.
That 'unsetup' api call deletes a bunch of links and then marks is_admin and is_active as false on the user object.
Updated by Ward Vandewege almost 3 years ago
Ready for review at bad2728b2ed147badcd67ff0d21be20d17f0c9ea on branch 18183-revoke-tokens-when-user-is-disabled
Updated by Peter Amstutz almost 3 years ago
Ward Vandewege wrote:
Ready for review at bad2728b2ed147badcd67ff0d21be20d17f0c9ea on branch 18183-revoke-tokens-when-user-is-disabled
LGTM
Updated by Ward Vandewege almost 3 years ago
Peter Amstutz wrote:
Ward Vandewege wrote:
Ready for review at bad2728b2ed147badcd67ff0d21be20d17f0c9ea on branch 18183-revoke-tokens-when-user-is-disabled
LGTM
Thanks, merged.
Updated by Ward Vandewege almost 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|e1e1a215d954c3337a969019da7f7becc8d14012.
Actions