--- title: "Digipass Dynamic Authentication Service" slug: "a3s-pg-digipass-dynamic-authentication-service-4-0" updated: 2026-11-11T09:48:46Z published: 2026-11-11T09:48:46Z canonical: "docs.onespan.com/a3s-pg-digipass-dynamic-authentication-service-4-0" --- > ## 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 Dynamic Authentication Service ## Description Several steps are necessary for a Digipass user authentication through the Digipass Dynamic Authentication Service. The authentication process depends on the authentication mode that has been programmed for a particular authenticator application. The authentication modes used with dynamic authentication are RO, CR, and MM. For a description of the authentication modes, refer to [Authenticator application authentication mode](/secsdks/docs/a3s-pg-digipass-data-model-4-0#authenticator-application-authentication-mode) ## Functionalities For a successful user authentication, Digipass Dynamic Authentication Service provides two functionalities: - Password validation - Challenge generation ## Workflows ### Response-Only authentication workflow Authenticating a user in Response-Only mode involves the following steps (see [Figure: Response-Only authentication workflow](/secsdks/docs/a3s-pg-digipass-dynamic-authentication-service-4-0#Fig_Response-Only_authentication_workflow)): 1. Retrieving the BLOB assigned to the user in the database using the user ID. 2. Submitting the BLOB and the OTP to Authentication Suite Server SDK. 3. Writing the BLOB updated by Authentication Suite Server SDK back to the database. 4. Interpreting the code returned by Authentication Suite Server SDK. ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/RO_authentication_workflow.png?sv=2026-02-06&spr=https&st=2026-11-16T15%3A47%3A36Z&se=2026-11-16T16%3A47%3A36Z&sr=b&sp=r&sig=7EJzVR0uaiugWaMICy6PkiXSchcUzdSR%2B6tbsob4gPE%3D) Figure: Response-Only authentication workflow ### Challenge/Response authentication workflow Authenticating a user in Challenge/Response mode involves the following steps (see [Figure: Challenge/Response authentication workflow](/secsdks/docs/a3s-pg-digipass-dynamic-authentication-service-4-0#Fig_Challenge_Response_authentication_workflow)): 1. Retrieving the BLOB assigned to the user in the database using the user ID. 2. Submitting the BLOB to Authentication Suite Server SDK to generate a challenge. 3. Writing the BLOB updated by Authentication Suite Server SDK back to the database. 4. Submitting the challenge to the user so they can generate the OTP. 5. Retrieving the BLOB assigned to the user in the database using the user ID. 6. Submitting the BLOB, the OTP and (optionally) the challenge to Authentication Suite Server SDK. 7. Writing the BLOB updated by Authentication Suite Server SDK. 8. Interpreting the code returned by Authentication Suite Server SDK. ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/CR_authentication_workflow.png?sv=2026-02-06&spr=https&st=2026-11-16T15%3A47%3A36Z&se=2026-11-16T16%3A47%3A36Z&sr=b&sp=r&sig=xSI89FDTTa0LU3QVwCm583ptVLQ3HSxZJrwHQ385hGI%3D) Figure: Challenge/Response authentication workflow