--- title: "Provisioning registration" slug: "oas-fullsdk-pg-provisioning-registration-3-29" updated: 2026-01-22T16:37:28Z published: 2026-01-22T16:37:28Z canonical: "docs.onespan.com/oas-fullsdk-pg-provisioning-registration-3-29" --- > ## 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. # Provisioning registration Standard provisioning registration can involve the following optional processes: - Assignment of a software authenticator to the user. - Creation of an activation code for the assigned software authenticator. OneSpan Authentication Server requires a successful user authentication before generating an activation code for the assigned authenticator. The following registration types are supported, based on the type of user authentication: - [Local authentication with the pre-loaded static password](/sec/docs/oas-fullsdk-pg-provisioning-registration-3-29#local-authentication-with-preloaded-static-passwords) - [Activation code gets encrypted with the pre-loaded static password](/sec/docs/oas-fullsdk-pg-provisioning-registration-3-29#activation-codes-encrypted-with-preloaded-static-passwords) - [Dynamic User Registration (DUR) using a back-end system for authentication](/sec/docs/oas-fullsdk-pg-provisioning-registration-3-29#dynamic-user-registration-dur-using-a-backend-system-for-authentication) Local authentication and activation code encryption with the pre-loaded static password are registration types that assume that user accounts and static passwords have been pre-loaded into OneSpan Authentication Server. ## Local authentication with pre-loaded static passwords For this operation to succeed, the following administrative tasks should be performed in OneSpan Authentication Server: To configure OneSpan Authentication Server for local authentication (with pre-loaded static passwords) 1. Register the client application. 2. Define a policy with the following settings: - Policy > Local Authentication: Digipass Only, DIGIPASS/Password during Grace Period, or DIGIPASS or Password - Policy > Back-End Authentication: None 3. Register the client component. 4. Assign the policy previously defined to the registered client application. 5. Import software authenticators. 6. Pre-load users with their static passwords. For more information about performing these tasks, see the [OneSpan Authentication Server Administrator Guide](/sec/docs/oas-administrator-guide-3-29). To execute this operation, the registered client application needs to send a `provisioningExecute` SOAP command to OneSpan Authentication Server, where the value for the `cmd` element is PROVISIONCMD_REGISTER. At a minimum, this SOAP command requires the following set of field attributes to perform this operation: - `PROVFLD_STATIC_PASSWORD` - `PROVFLD_USERID` - `PROVFLD_COMPONENT_TYPE` For more information about the required and optional attributes for this command, see [SOAP provisioning](/sec/docs/oas-fullsdk-soapref-soap-provisioning-3-29). > A client application that uses the DP4Web Provisioning Sample Client component type will typically send the following SOAP command to register user test1 for this provisioning scenario: > > ```xml >    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >    xmlns:xsd="http://www.w3.org/2001/XMLSchema" >    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >    xmlns:prov="http://www.vasco.com/IdentikeyServer/IdentikeyTypes/Provisioning"> >     >     >         >            PROVISIONCMD_REGISTER >             >                 >                    233655275246515E5336245456302C2D55335D5720455A2952335C5254475A53 >                    PROVFLD_ALEA >                 >                 >                    DP4Web Provisioning Sample Client >                    PROVFLD_COMPONENT_TYPE >                 >                 >                    test1 >                    PROVFLD_USERID >                 >                 >                    passwd >                    PROVFLD_STATIC_PASSWORD >                 >             >         >     > > ``` > > In this example, the specified user's password is passwd. OneSpan Authentication Server will verify this locally before generating an activation code. ## Activation codes encrypted with pre-loaded static passwords For this operation to succeed, the following administrative tasks should be performed in OneSpan Authentication Server: To configure OneSpan Authentication Server to provide activation codes encrypted with pre-loaded static passwords 1. Register the client application. 2. Define a provisioning policy with the following settings: - **Policy > Local Authentication**: None - **Policy > Back-End Authentication**: None 3. Assign the policy previously defined to the registered client application. 4. Import software authenticators. 5. Pre-load users with their static passwords. For more information about performing these tasks, see the [OneSpan Authentication Server Administrator Guide](/sec/docs/oas-administrator-guide-3-29). To execute this operation, the registered client application needs to send a `provisioningExecute` SOAP command to OneSpan Authentication Server, where the value for the `cmd` element is `PROVISIONCMD_REGISTER`. At a minimum, this SOAP command requires the following set of field attributes to perform this operation: - `PROVFLD_USERID` - `PROVFLD_COMPONENT_TYPE` For more information about the required and optional attributes for this command, see [SOAP provisioning](/sec/docs/oas-fullsdk-soapref-soap-provisioning-3-29). > A client application that uses the DP4Web Provisioning Sample Client component type will typically send the following SOAP command to register user test1 for this provisioning scenario: > > ```xml >    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >    xmlns:xsd="http://www.w3.org/2001/XMLSchema" >    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >    xmlns:prov="http://www.vasco.com/IdentikeyServer/IdentikeyTypes/Provisioning"> >     >     >         >            PROVISIONCMD_REGISTER >             >                 >                    233655275246515E5336245456302C2D55335D5720455A2952335C5254475A53 >                    PROVFLD_ALEA >                 >                 >                    DP4Web Provisioning Sample Client >                    PROVFLD_COMPONENT_TYPE >                 >                 >                    test >                    PROVFLD_USERID >                 >             >         >     > > ``` ## Dynamic user registration (DUR) using a back-end system for authentication For this operation to succeed, the following administrative tasks should be performed in OneSpan Authentication Server: To configure OneSpan Authentication Server for Dynamic User Registration (DUR) using a back-end system for authentication 1. Import software authenticators. 2. Define a provisioning policy with the following settings: - **Policy > Local Authentication**: DIGIPASS/Password during Grace Period or DIGIPASS or Password - **Policy > Back-End Authentication**: If Needed - **Policy > Back-End Protocol**: Windows, RADIUS, or Custom Name - **User > Dynamic User Registration**: Enabled 3. Register client application. 4. Assign the policy previously defined to the registered client application. 5. Define users. For more information about performing these tasks, see the [OneSpan Authentication Server Administrator Guide](/sec/docs/oas-administrator-guide-3-29). For more information about supported provisioning scenarios, see the [Provisioning scenarios](/sec/docs/oas-pg-provisioning-scenarios-3-29). To execute this operation, the registered client application needs to send a `provisioningExecute` SOAP command to OneSpan Authentication Server, where the value for the `cmd` element is PROVISIONCMD_REGISTER. At a minimum, this SOAP command requires the following set of field attributes to perform this operation: - `PROVFLD_STATIC_PASSWORD` - `PROVFLD_USERID` - `PROVFLD_COMPONENT_TYPE` For more information about the required and optional attributes for this command, see [SOAP provisioning](/sec/docs/oas-fullsdk-soapref-soap-provisioning-3-29). > A client application that uses the DP4Web Provisioning Sample Client component type will typically send the following SOAP command to register user test1 for this provisioning scenario: > > ```xml >    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >    xmlns:xsd="http://www.w3.org/2001/XMLSchema" >    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >    xmlns:prov="http://www.vasco.com/IdentikeyServer/IdentikeyTypes/Provisioning"> >     >     >         >            PROVISIONCMD_REGISTER >             >                 >                    233655275246515E5336245456302C2D55335D5720455A2952335C5254475A53 >                    PROVFLD_ALEA >                 >                 >                    DP4Web Provisioning Sample Client >                    PROVFLD_COMPONENT_TYPE >                 >                 >                    test1 >                    PROVFLD_USERID >                 >                 >                    passwd >                    PROVFLD_STATIC_PASSWORD >                 >             >         >     > > ``` > > In this example, OneSpan Authentication Server will verify the specified user's password (i.e. passwd) with the configured back-end system before generating an activation code.