silverstripe-admin
silverstripe-admin copied to clipboard
Indeterminate behaviour when editing a member that is a "default admin"
Like Schrödinger's cat, default admin is both a user, and not a user - in that the account exists always, but only while being observed. Editing this magically inserted default record causes strange behaviour.
Recreate:
- Install SilverStripe using
SS_DEFAULT_ADMIN_...
combo ofadmin:password
- Log in to
/admin/security
usingadmin:password
- Open only user (
admin
) - Change "Default Admin" email address
- admin + admin@localhost
- save ("Apply changes").
- wait for session to time out, perhaps whilst you eat lunch.
- Click save again.
- When presented with the "please re-authenticate that you are you" modal, enter the password (
password
) - Be told by the modal reload that your user does not exist, you are a fraud, and watch your whole DEFAULT_ADMIN life crumble before your eyes as if it were all an elaborate fabrication.
- visit
/admin/security
and try to log in asadmin@localhost:password
- and be denied also. - visit
/admin/security
and log in as normal; usingadmin:password
still. - Now there are two "Default Admin" users -
admin
andadmin@localhost