Limit the Number of Personal Access Tokens a User Can Create
An organization administrator can limit the maximum number of tokens a user in the organization is allowed to create. This action can prevent users from creating excessive numbers of personal access tokens. It also makes it easier for an administrator to maintain existing tokens. The Organization Properties page provides an option for controlling the maximum number of tokens each user can create. The default limit is 10 personal access tokens per user, but this limit can be increased to a maximum of 50 tokens per user. The set value applies to all users, including the organization administrator, who sets the limit.
- In the
left navigator, click
Organization
.
After the check box is selected and a limit set, the User Preferences, Maven Browse, and NPM Browse pages will use the set limit to deal with the situation that arises when a user's token limit has been reached. When the limit is decreased, the new limit applies to new token creation only. It doesn't force users to delete any of their existing tokens. In other words, it doesn't affect the number of already-created tokens but it can prevent them from creating any new tokens until they delete enough of the existing tokens to be under the limit.
To remove the limit, deselect the Enforce a per-user limit on the number of personal access tokens check box.
- An "Expires Soon" status label is displayed next to the
token 5 days before the actual expiration date.
Description of the illustration token-expire-soon-warning-label.png
- An email notification is sent to the user 5 days before the
user’s personal token is about to expire.
Description of the illustration token-expiration-warning-email.png