Configuring your user settings
Anaconda Enterprise maintains settings related to your user account, based on how the system was configured by your Administrator. There are times when you may need to update the information related to your user account—to change your password, add credentials required to access a version control repository, or add secrets that can be used to access file systems, data stores and other resources implemented by your organization, for example.
To access your account settings, click the User icon in the upper-right corner and select the Settings option in the pull-down.
Click Advanced Settings to configure the following settings for your Anaconda Enterprise account:
- To change the email or name associated with your account, edit the associated field for the Account.
- To change the password you use to log in to Anaconda Enterprise, select Password.
- To enable two-factor authentication for your account, select Authenticator.
- To view a history of your sessions using Anaconda Enterprise, select Sessions. You can also log out of all sessions in one click here.
- To view a list of AE applications currently running and the permissions you have been granted, select Applications.
- To view a log of all activity related to your account, select Log.
Fields that you are not permitted to edit appear grayed / disabled.
Configuring access to version control
If your Administrator has configured Anaconda Enterprise to use a supported version control repository other than the internal GitHub server, you’ll need to provide your credentials to be able to access that repository. Anaconda recommends you create an ever-lasting token, so you can retain permanent access to your files from within Anaconda Enterprise.
Your auth token must also have the following permissions:
| External Repository | Permissions Required |
|---|---|
| Bitbucket Enterprise | Admin access for Projects and Repositories |
| GitHub Enterprise | repo:status, repo_deployment, public_repo, repo:invite, and delete_repo |
| GitLab Enterprise | Check the api access check box when creating your access token. |
You’ll be prompted to configure your personal access token when you attempt to create your first project in Anaconda Enterprise, if you haven’t already done so.
- Under External Version Control Credentials, click Add.
- Enter the username and personal access token you use to access the repository in the relevant fields.
- Click Add to update the platform with your credentials.
To manage credentials that you’ve added, click on the command menu for the credentials, then choose whether you want to edit or delete them.
Now that you’ve configured access, you’ll be able access the repository within your sessions and deployments without having to leave the platform. Anaconda Enterprise creates a repository for each project that you create.
Storing secrets
Anaconda Enterprise enables you to securely store information such as user names, passwords, API keys, or authentication tokens. Any secrets you add will be available across sessions and deployments for all projects associated with your account–but the values are not shared with other users.
Secrets are mounted into deployments and sessions as files, where the name of the file matches the name of the secret. Each file stores the value provided for that secret. You can access the contents of these files from within your projects, to access file systems, data stores and other resources implemented by your organization.
We highly recommend you use the secrets store over including credentials in your project, due to the potential security risk associated with storing them in version control.
- Under Secrets, click Add.
- Enter a Name and Value for the secrets you want to store, then click Add.
Secret names can contain alphanumeric characters and underscores only—not special characters or paths.
Any secrets you add are listed by name. To manage your secrets, click on the command menu for the item then choose whether you want to edit, delete or copy the name of the secret.
To access credentials you’ve added within a session, deployment, or scheduled job:
- Open a new terminal window.
- Change directory to the location where the secrets are stored:
/var/run/secrets/user_credentials/. - Run
cat <credential_key>—replacingcredential_keywith the actual key name—to display the value you entered when you added the secret. - Use the value to access the file system, data store or other resource as needed. See Loading data for more information.