TID Provisioning for Multi-Device Licensing (Policy)
The following is an overview of the relevant default settings of provisioning for multi-device licensing with OneSpan Cloud Authentication.
- Parent policy: IDENTIKEY Provisioning for Multi-Device Licensing
|Parameter name||Default value||Description|
|local_auth||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 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.
The method by which a user has to request a Virtual Mobile Authenticator login. The request is made in the password field during login. The request will be ignored if the user does not have a Virtual Mobile Authenticator assigned.
Types 01, 03, and 07 are MDL instances derived from the DAL10 authenticator type.
Authenticator Type Limit
Limits of authenticator instances per authenticator type.
This setting allows you to restrict the maximum number of assigned authenticators per user for specific authenticator types. If you need to have more than one authenticator provided to your users, you should still limit the number to avoid that too many authenticators (and/or instances) are assigned to or activated for single users.
For single-device licensing, it is possible to limit the number of assigned authenticators; for multi-device activation/multi-device licensing the setting limits the number of assigned authenticator licenses and activated authenticator instances.