Login Setting

1) The Login Setting can be completed in the System Permission to meet different security and display needs of users.

2) In the Login Setting, you can make settings based on your own needs, such as whether to keep logged in, single login, display login information, login verification, login timeout and others.

1. Single Login

1) When enabled, Single login ensures an account only logins on one site at a time:

• In the Login Setting, two browsers on the same machine are considered as two sites. Therefore, when the [Single Login] is enabled, you cannot log on two browsers on the same machine simultaneously.

• After enabling [Single Login], simultaneous login to a browser and an App will not conflict. However, a prompt will appear in case of simultaneous login to two Apps.

2) The default option of Single Login is [Later login kicks out earlier login]. Suppose you have logged in to the Decision-making Platform on Computer A, then you can log in to the Decision-making Platform on Computer B yet a prompt will show up on Computer A, and the login on Computer A will be kicked out if you click [OK] on the prompt.

3) You can also check [Login is forbidden if already logged in]. In this case, if you have logged in the Decision-making Platform on computer A, then you cannot log in on Computer B, and a prompt will pop up, asking you to modify the password.

2. Last login information

You can enable [Last login prompt] to inform you of last login IP address, time and location. 

3. Login timeout

The system will kick you out after 60 minutes, which is the default login timeout. You can customize the Login timeout. The login timeout should not be shorter than 10 minutes. 

Note:

• Password strategy is not applicable when using [user sync dataset], [LDAP AUTH], [HTTP AUTH] for versions before 2020-11-02.

• Password strategy is not applicable for users who cannot edit their passwords, with version of 2020-11-02 and after.

• If Jar is updated according to this, super-admin and synchronized users with [info editable] will need to change the password.
  

1. Forget my password

1) If [Forget my password] is enabled, you set the method of validation when user forgets the password.

2) You need to enable maibox or SMS service first. For the setting instruction, see: Mailbox management, SMS Service

3) Each user must have corresponding Email or Phone number in the user management.

Note: Mobile devices support Forget Password.

Instructions on version combinations are as follow:

2. Password update

1) After enabling [Password Update], you need to change the password regularly.

2) The default update cycle is 90 days. You can customize the update cycle either by entering the number of days or by selecting the number of days from the drop-down box. The customized update cycle must not be less than 7 days. In the drop-down box, 1 month equals to 30 days. 

3. Password limit

1) You can set: the minimum length of the password, and whether the password must contain any number, uppercase and lowercase letter, or symbol.

2) If the original password fails to meet the requirements, the system will jump to the Change Password page when you log on the Decision-making Platform.

4. Password check

1) The Password Check is not enabled by default. In this case, you can use any one of previous passwords as the current password.

2) If Password Check is enabled, when the user changes the password, it is forbidden to use previous N passwords, where N is an integer not less than 1 and not greater than 10. 

5. Forced password change

1) The Forced Password Change is not enabled by default. In this case, you can use the initial password.

2) After enabling Forced Password Change, if you login on the Decision-making Platform with the initial password, the system will prompt you to change the password.

6. Authentication for password change

1) After the Authenticationis enabled, you need to verify your identity first when you change the password.

2) For oversea users, you can only use the email for authentication. You should bind the account to your email first, then you will receive an email for the confirmation of the binding.

1. Slider verification

1) After enabling [Slider], you will be asked to complete slider verification if you enter the wrong password.

2) If you are asked to complete slider verification, you should drag the slider to the correct position, and enter the correct username and password to log in to the Decision-making Platform.

2. Email authentication

After enabling [Email] button, you need to verify your identity after entering the username and password to log in to the Decision-making Platform. After clicking [Get the verification code], you will receive an email containing a verification code from the system, and you should enter the verification code to log in.

1) By default, the Login Lock is not enabled. In this case, you can try the password for numerous times. After enabling the Login Lock, if you enter the wrong password 5 times in succession, the account or IP will be locked for 60 minutes, which are the default error time limit and lock time. Administrator can customize the error time limit and lock time.

2) The Lock Target can be Account or IP:

• If you choose to lock account, then when the account is locked, changing devices to log in will not work. However, other accounts can log in on the same device.

• If you choose to lock IP, then when the IP is locked on one device, all accounts are locked on the device, but you log in on another device.

3) By default, [Lock Admin Account] is not enabled. In this case, the administrator can enter the password for unlimited times. After enabling [Lock Admin Account], the administrator, the same as a normal user, should be subject to the restriction of [Login Lock].

4) The targets will be unlocked after the lock time, but the administrator can manually unlock targets in the Decision-making Platform.

After logging in to the [Decision-making Platform], the administrator will see all locked targets and may unlock any account here.