Provisioning for Multi-Device Licensing with Static Password (Policy)
The following is an overview of the relevant default settings of provisioning for multi-device licensing with a static password.
- Parent policy: IDENTIKEY Provisioning for Multi-Device Licensing
|Parameter name||Default value||Description|
DIGIPASS or Password
When local authentication is used, there are two factors that determine whether an authenticator is used for authentication – any policy restrictions on authenticator types and/or applications that can be used and whether the user account has any assigned authenticator that meets the restrictions. For example, if the policy requires a certain authenticator type, but the user has a different type, they cannot use the authenticator for authentication under that policy.
This setting also affects the provisioning registration process.
Maximum Age in Days
This specifies the maximum amount of time in days during which a local static password is valid. After this time, the password expires. Applies to the local authentication mode DIGIPASS or Password only.
If set to 0, the local static password never expires. Select this to disable local static password expiration if you are using back-end authentication, and to rely on the back-end system to enforce password expiration.
Possible values: 0–9999
Minimum Age in Days
This specifies the minimum amount of time in days a static password must be used before it can be changed. It applies to the local authentication mode DIGIPASS or Password only.
Maximum Days Between Authentications
This setting specifies the number of days a user account can remain inactive before it is suspended. If the account has been suspended, the user will not be able to log on. The user will be notified during authentication that the user account has been suspended. By default, a user account expires when no operations have been performed during the last 90 days.
You can reactivate a suspended user account with the Reset Last Authentication Time action in the USERS >User Account tab.
Setting this value to 0 effectively disables this feature. User accounts that are suspended at the time the feature is being disabled will become active again with the next successful user authentication.