There is a method to limit one token per User ID in the Authentication Manager database and an administrator will require command line access with a restart of Authentication Manager services.
 

Before following the instructions below, it would be advisable to have a backup of the Authentication Manager database. Follow the instructions on How to create a Backup Using Back Up Now.

Instructions 

1. If not already enabled, enable secure shell on the appliance.
2. Login to the primary Authentication Manager server as rsaadmin and enter the operating system password.

Note that during Quick Setup another user name may have been selected. Use that user name to login.

3. Navigate to the /opt/rsa/am/utils folder:

login as: rsaadmin
Using keyboard-interactive authentication.
Password: <enter operating system password>
Last login: Tue Aug 28 14:18:12 2018 from jumphost.vcloud.local
RSA Authentication Manager Installation Directory: /opt/rsa/am

4. Navigate to /opt/rsa/am/utils:

​rsaadmin@am82p:~> cd /opt/rsa/am/utils 
rsaadmin@am82p:/opt/rsa/am/utils> 

5. Carefully enter the following command and provide the Operations Console admin password when prompted:

rsaadmin@am82p:/opt/rsa/am/utils> ./rsautil store -o <enter Operations Console administrator name> -a add_config auth_manager.admin.maximum_usable_tokens 1 GLOBAL 501
Please enter OC Administrator password: <enter Operations Console administrator password>
psql.bin:/tmp/819c55ab-0e79-49cb-a420-5f4b4d9094ae3515872605838824841.sql:108: NOTICE:   Added the new configuration parameter 
"auth_manager.admin.maximum_usable_tokens" with the value "1"
 add_config
------------

(1 row)

rsaadmin@am82p:/opt/rsa/am/utils>

6. Restart all Authentication Manager services on the primary server:

/opt/rsa/am/server/rsaserv restart all

7. Repeat the service restart on all replicas.

The default value for auth_manager.admin.maximum_usable_tokens is 3.  The same procedure above can be used to set the usable token value to 3 or 2.

8. After restarting the Authentication Manager services on the primary and replica(s), an administrator will get the following message on the primary's Security Console when trying to assign more than one token to a selected user.