--- title: "DIGIPASS – Authenticator application tabs" slug: "oas-was-csh-ux-digipass-authenticator-application-3-28" updated: 2025-10-15T09:05:39Z published: 2025-10-15T09:14:42Z canonical: "docs.onespan.com/oas-was-csh-ux-digipass-authenticator-application-3-28" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # DIGIPASS – Authenticator application tabs There will be one application tab per authentication application associated with the authenticator, the name of each tab is the respective application name. | Field name | Description | | --- | --- | | Application status | This field indicates whether the application is active or not. If it is not active, it cannot be used for authentication, provisioning or signature validation. Read-only. The Activate Application and Deactivate Application commands must be used to change this. | | Application Type | Read-only. This field displays the type of the selected authenticator application. - RO. Response-Only. - CR. Challenge/Response. - SG. Signature. - MM. Multi-Mode, which is a combination of two or more of the above application types and used mainly for DIGIPASS for Web. - MA. Master Activation. Applies only devices compatible with the multi-device activation and multi-device licensing. | | Secure Channel Support | This field indicates whether the application supports Secure Channel. | | Application Info | | This list indicates various internal settings of the authenticator application. They are not edited directly. Some are implicitly updated by some authenticator operations such as one-time password verification, others represent programming parameters and never change. | | Attribute | The application attributes. There will be one row per attribute. Each row will show the name of the attribute, and the value of the attribute. | | Value | The value of the application attribute. | | Update History | | Created On | Read-only. The date and time that the record was created. | | Modified On | Read-only. The date and time that the record was last modified. | ## Available actions Depending on the application type, one or more of the following actions will be available: - [Activate Application](/sec/docs/oas-was-csh-ux-activate-application-3-28)/ [Deactivate Application](/sec/docs/oas-was-csh-ux-deactivate-application-3-28). Actual text/action to be displayed should be based on the current authenticator application status. - [Unlock DIGIPASS](/sec/docs/oas-was-csh-ux-unlock-digipass-3-28). Use this action to unlock an authenticator that has been locked, because the user supplied an incorrect PIN too many times. - [Test OTP](/sec/docs/oas-was-csh-ux-test-otp-3-28). Only displayed when the application type equals RO or MM. - [Test Signature](/sec/docs/oas-was-csh-ux-test-signature-3-28). Only displayed when the application type equals SG or MM. - [Test VDP](/sec/docs/oas-was-csh-ux-test-vdp-3-28) - Test BVDP. - [Reset PIN](/sec/docs/oas-was-csh-ux-reset-pin-3-28) - [Force PIN Change](/sec/docs/oas-was-csh-ux-force-pin-change-3-28) - Set PIN - Reset Error Count. Use this action to reset the error count of an authenticator application. This function can also be used when either the identification threshold or signature threshold for a policy is reached and prevents authentication or signature validation using this authenticator application (see [POLICIES – DP Control Parameters (tab)](/sec/docs/oas-was-csh-ux-policies-dp-control-parameters-3-28)). - [Reset Application](/sec/docs/oas-was-csh-ux-reset-application-3-28) - [Delete Application](/sec/docs/oas-was-csh-ux-delete-application-3-28). This action is NOT available for master activation application authenticators (in the context of multi-device licensing and Activation) - Set Event Counter - Enable Server PIN - Disable Server PIN For more information about authenticator application types, see [Authenticator application types](/sec/docs/oas-pg-authenticator-application-types-3-28).