User management
ASKCOS now includes basic user management which is accessible locally at 0.0.0.0/admin-login. By default, a superuser account will be created upon the initial deployment. This superuser's credentials are shown below:
username: askcos_admin
password: reallybadpassword
PLEASE NOTE THE FOLLOWING TWO IMPORTANT POINTS
- The default superuser
askcos_admin
will be recreated upon restart if there is no other superuser account. - Only superusers can add, delete, promote and demote all other superusers.
The expectation is that the person who deploys ASKCOS (the deployer) will:
- Log in with
askcos_admin
to the admin/user page (e.g., at 0.0.0.0/admin-login) immediately after the initial deployment. - Create their own superuser account.
- Logout of the
askcos_admin
account and re-login with their new superuser account. - Delete the
askcos_admin
account.
This way only the deployer will, initially, have full control over who can become an admin (Point 2 above). This will change when other superuser accounts have been created.
To prevent a situation where no superuser accounts exist (e.g., somehow all superuser accounts were accidentally deleted), the askcos_admin
superuser account will be recreated upon a restart (Point 1 above). The deployer should then repeat the steps above to harden the deployment.
Once logged into admin-login
, the views and functionalities are pretty self-explanatory.
You can promote a normal user to an admin user via MAKE ADMIN
, reset the password for users (new passwords will need to be sent directly to the user), etc.
Moreover, it is possible to do a BULK OPERATION
on a set of user accounts. Simply select all the appropriate accounts by clicking on the checkbox beside the username and the BULK OPERATION
dropdown will appear with the various operations available. In the example below, the guest_ accounts are going to be deleted.
Don't be overwhelmed by the number of guest_ user accounts. A new guest_ user account gets created every time a user chooses to CONTINUE AS GUEST rather than register/login. This is by design for easy cleanup later.