Manage Users
Everything you need to know about managing users within your deployment.
Last updated
Everything you need to know about managing users within your deployment.
Last updated
A user was initially specified and created during the deployment process. As with any new user, you were required to change your password as you signed in for the first time. The Manage Users section of the console is to extend the management of user(s) beyond that initial setup. From the Manage Users page you can create additional users (assuming your user is an Admin), delete users and modify users in the form of assigning them to groups and changing their roles.
Managing users involves creating, modifying, deleting or activating/deactivating their accounts. At the time of creation you will also assign them one or multiple groups to belong to. You can change the group assignment later as well.
You may not be using Groups to organize your accounts. There is always one group created by default, the Primary group. In this situation you would specify Primary as the group value.
As seen below you are presented a simple page with the list of existing users. Directly after install you will only have one user in the list that was created during deployment. You can add more users as desired from this page and they will be reflected here as well.
Creating a new account is a simple process. Click the Create User button.
Provide a User Name, a valid Email Address, the User Access Level and a Group to belong to. An email will be sent to the specified email address with a login URL and Temporary Password. There are fourUser Access Levels: Admin, User, Read Only, and API. The difference being Admin has access to all screens and configuration capabilities, while the User will not be able to create additional users or modify any of the configuration. Read Only users cannot perform actions. They can view pages, metrics, etc. but they cannot protect buckets, make changes, etc. API access level allows a user to execute API calls, but not login to the console at all.
User account types can see all dashboards and buckets and can enable / disable buckets.
After creating the new user, they will be in a pending state until they have logged in and reset their password. They have 7 days to complete this with the password that was sent to them. After that time period, you will have to delete and recreate the user.
Selecting Change Groups pops open the following:
Selecting Change Role pops open the following:
In order to delete a user, you must disable the user first.
Setting up API Access for a user enables their username and password to be used to send file scan requests against the configured API Agents. You must associate a user to an Account Number track usage. Because API scanning can operate outside the bounds of Amazon S3, we have to fabricate a usage tracking mechanism. So any API file scanning this user does will be tied to the Account Number associated.
To enable a user for API access you select the Actions menu for the user and select Enable API Access
You'll be prompted to pick an account to associate to the user and then click the Enable Access button
Afterwards you will notice they have an Account Number showing under the API Account column
If you want to create an api-only user without console access, make sure to set the role to API
For more information on API based file scanning and what APIs are available, check out the API Scanning Overview page.
Just as you did when you first logged into the console, you need to provide your current password and then what you'd like for your new password. Be sure to follow the rules as described at the bottom of the page.
You cannot reset another user's password from the console. Have the user leverage the Forgot Password link at the login screen.
You'll be presented your user information overview and the option to enable MFA. Clicking the Enable... link will start the process to setup MFA. You can also identify if you have saved the device you are currently accessing from as "remembered" so you do not have to use MFA each time.
Enable MFA Settings:
Click Enable...
Enter your existing password and click Generate Setup Key
Use your one time password application of choice to scan the QR code and enter the first one time code and click the Verify button
On the final screen, click the Enable MFA button
You will now be presented with your user settings showing MFA is enabled.
The next time you login you will be prompted to enter the OTP after the standard username / password login screen. You can choose to save this computer off or not so you have to enter MFA each time you login.
You can find more information on implementing Single Sign-On (SSO) for your deployment by going to this FAQ answer.
To modify an existing user, select the action menu () on the particular user's row. Now select the appropriate action you'd like to take: Change Groups, Change Role, Disable User or Enable API Access. If the user has already been disabled you will be given an option to delete the user.
To change your own password, you will select the user icon in the upper right corner of the console and select Change Password from the menu.
To turn MFA on, you will select the user icon in the upper right corner of the console and select Settings from the menu.
To sign out of the console, you will select the user icon in the upper right corner of the console and select Sign Out from the menu.
