POLICIES – Policy (tab)

Specifies whether authentication requests using the policy will be handled by OneSpan Authentication Server using local authentication. For more information about local authentication and back-end authentication, refer to the OneSpan Authentication Server Product Guide, Section "Authenticating Users".

When local authentication is used, there are two factors that determine whether authentication with an authenticator is used – 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. For more information, refer to the OneSpan Authentication Server Product Guide, Section "Software authenticator provisioning".

Possible values:

• Default. Use the setting of the parent policy.
• None. OneSpan Authentication Server will not use local authentication under this policy. The authentications may be handled using back-end authentication or not handled at all by OneSpan Authentication Server.
• DIGIPASS Only. OneSpan Authentication Server will always use local authentication under this policy, using authentication with authenticator. If authentication with authenticator is not possible, the user cannot log in. Back-end authentication may also be used.
• DIGIPASS/Password During Grace Period. OneSpan Authentication Server will always use local authentication under this policy, possibly using Digipass Authentication for Windows Logon, if applicable. The static password can only be used within a (configurable) grace period until an authenticator is used the first time. Back-end authentication may also be used.
• DIGIPASS or Password. This authentication mode allows users to permanently use their static password or their authenticator. This is possible even after the grace period has expired and/or they have previously already used their authenticator for authentication. The grace period also expires after a successful MDL activation, either using an OTP or a signature validation. In the context of the authentication scenario, use of this authentication mode is subject to licensing. For provisioning, this authentication mode is license-free.

Specifies the protocol to be used for back-end authentication.

If you have your own back-end authentication engines, they will have protocol names to identify them. The name for the required engine must be defined in the back-end protocol for the policy.

The following standard authentication options are available:

• Windows(this is only available when OneSpan Authentication Server runs on Windows)
• RADIUS
• NetIQ eDirectory
• Microsoft Active Directory
• IBM Security Directory Server