You might want to limit the number of times a specific user can log in. For example, if you set a user's login limit to three, iChain does not let that person log in again after the login limit is reached. If the user opens multiple sessions, iChain closes the first login instance when the limit is reached.
To set up the concurrent login option, enter the login restriction settings in the iChain console.
NOTE:Concurrent Login Restrictions should not be used in a Session Broker setting.
Open the iChain console screen.
Type the following command:
set authentication limitconcurrentlogins = (yes/no)
This turns on the concurrent login restriction feature. For example
set authentication limitconcurrentlylogin=yes
When it is set to No, the concurrent login setting is disabled. When it is set to Yes, use the commands in Step 3 to control the functioning of the feature.
If you are using SSL as an authentication method for your accelerators, make sure that the Send and Error Page When a Mutual SSL Error option is enabled. Otherwise, a blank page appears when users reach their authentication limit.
Set up the concurrent login option using the following commands:
Type set authentication maxlogins = (nonzero positive integer), then click Apply.
This sets the number of concurrent logins that are allowed. For example
set authentication maxlogins=4 (or a number you choose).
After the maximum number of logins is reached, the user is denied access or an older instance is logged out.
Type set authentication logoutoldest= (yes/no).
This determines what action to take when the maximum number of logins is reached. For example, set authentication logoutoldest=yes.
When it is set to Yes, the least recently accessed connection of the user is logged out and a new login occurs. When it is set to No, the new login is rejected with a message indicating that the maximum number of logins has been exceeded. The default is No.
After you set up the concurrent login option, reboot the iChain Proxy Server.