Access Tokens Page
Access Tokens
Add and manage Access Tokens for installing the Evo Agent through this page
The Admin must have access to the Role that generates the Access Tokens. The role is "Access token".
Whenever you need to install the Evo Login agent on a customer site, you will need an Access Token created.
Access Tokens allow an Evo directory to have its own encryption key tied to the Access Token. The access token can be time-limited which allows for better security. Every directory can have one or multiple APIKey/Secrets.
DO NOTE: Secret Keys are only exposed at the time of creating an Access Token. If you lose a Secret Key, you can create a NEW Access Token for the same Customer/Directory. This will not effect previous Credential Provider installs.
- Give the token a name, select the appropriate Customer and Directory you'd like the token to be associated to.
- Give it an expiration date. At that date, all communication between agents installed with that token and the Evo Cloud will be cut off. Admin users will get notifications in advance that the token is about to expire. If you'd like to extend the date, edit the created token on the right and you'll be able to change the date.
- Once created, the token details will appear on screen. Store these values in a secure location, the secret value will not be accessible after you complete the token setup process. Then, use these details to fill in the credentials for the Credential Provider when prompted.
Access Token Expirations
As you set up your Access Tokens within the Evo Portal, you'll notice that you'll need to set a date in the future when that Access Token will expire. As time goes on, it may be difficult to remember when these tokens expire and you may forget that it even has an expiration date to begin with! We send Access Token Expiration Emails to remind you when a token is expiring and what steps you need to take.
The emails are sent out 30 days, 7 days, and 1 day prior to the expiration date. Global Admins and Admin Users who have the proper Customer Access with the following roles enabled (either directly, or via group membership) within Role-Based Permissions will receive the notification emails:
- Add Access Token
- Delete Access Token
- Edit Access Token
The email received will look as such:
If you do not wish to receive these emails, remove the affected users' roles and/or remove their access from the customer they will be opted out of receiving these emails.