thunderbird_accounts.authentication.admin.actions
Functions
|
|
|
Backfill's recovery emails from user with |
Run through some common edge-cases to hopefully repair a broken relationship to a stalwart account |
|
|
|
|
Delete every Keycloak TOTP credential for the selected users. |
|
- thunderbird_accounts.authentication.admin.actions.admin_fix_broken_stalwart_account(modeladmin, request, queryset)[source]
Run through some common edge-cases to hopefully repair a broken relationship to a stalwart account
- thunderbird_accounts.authentication.admin.actions.admin_backfill_recovery_email(modeladmin, request, queryset)[source]
Backfill’s recovery emails from user with
nullrecovery emails in this system and a valid one in Keycloak.Displays the following messages on the admin panel after the action is performed: * Updated: The number of user’s that have been successfully updated with their recovery email. * Skipped: The number of user’s who were skipped because they don’t have a valid recovery email in Keycloak. * Failed: The number of user’s that exist in this system but do not exist in Keycloak.
- thunderbird_accounts.authentication.admin.actions.admin_reset_totp_credentials(modeladmin, request, queryset)[source]
Delete every Keycloak TOTP credential for the selected users.
First invocation (no apply=1) renders a confirmation page listing the affected users; the form posts back here with apply=1 to actually delete the credentials.
Recovery codes are deleted alongside the authenticator: they are strictly a backup for the authenticator app, so leaving them behind would strand the user on a codes-only second factor that Keycloak burns down to nothing as codes are spent. This mirrors the self-service removal cascade in
remove_totp_credential.