Product Documentation
ADC
14.1-Current Release 13.1
View PDF

Native OTP support for authentication

November 18, 2025
Contributed by: 
C

NetScaler supports one-time passwords (OTPs) without having to use a third-party server. OTP is a highly secure method of authentication, as the generated passcodes are random. In the past, specialized companies like RSA provided OTPs through devices that generated random numbers.

In addition to reducing capital and operating expenses, this feature enhances the administrator’s control by keeping the entire configuration on the NetScaler appliance.

Points to note:

  • The NetScaler administrator must configure an interface to manage and validate user devices because third-party servers are no longer needed.

  • The native OTP solution does not support the SAML logout feature.

User must be registered with a NetScaler virtual server to use the OTP solution. Registration is required only once per unique device, and can be restricted to certain environments. Configuring and validation of a registered user is similar to configuring an extra authentication policy.

Advantages of native OTP support

  • Reduces operating cost by eliminating the need to have an extra infrastructure on an authenticating server in addition to the Active Directory.
  • Consolidates configuration only to NetScaler appliance thus offering great control to administrators.
  • Eliminates the client’s dependence on an extra authentication server for generating a number expected by clients.

Native OTP workflow

The native OTP solution is a two-fold process and the workflow is classified as the following:

  • Device registration
  • End user login

Important:

You can skip the registration process if you are using third-party solutions or managing other devices apart from the NetScaler appliance. The final string that you add must be in the NetScaler specified format.

The following figure depicts the device registration flow to register a new device to receive OTP.

OTP workflow

Note:

The device registration can be done using any number of factors. The single factor (as specified in the previous figure) is used as an example to explain the device registration process. For more details, see Recommended native OTP configurations for device registration.

The following figure depicts the verification of OTP through the registered device.

OTP verification workflow

The following figure depicts the device registration and management flow.

Device registration and management

The following figure depicts the end user flow for the Native OTP feature.

End user workflow

Prerequisites

To use the native OTP feature, make sure that the following prerequisites are met.

  • NetScaler feature release version is 12.0 build 51.24 and later.
  • Advanced or Premium edition license is installed on NetScaler Gateway.
  • NetScaler is configured with management IP and the management console is accessible both using a browser and command line.
  • NetScaler is configured with authentication, authorization, and auditing virtual server to authenticate users. For more information, see Authentication virtual server
  • NetScaler appliance is configured with Unified Gateway and the authentication, authorization, and auditing profile is assigned to the Gateway virtual server.
  • Native OTP solution is restricted to nFactor authentication flow. Advanced policies are required to configure the solution. For more details, see Configuring nFactor authentication.

Also ensure the following for Active Directory:

  • A minimum attribute length of 256 characters.
  • The attribute type must be ‘DirectoryString’ such as UserParameters. These attributes can hold string values.
  • Attribute string type must be Unicode, if the device name is in non-English characters.
  • NetScaler LDAP administrator must have write access to the selected AD attribute.
  • NetScaler appliance and client machine must be synced to a common Network Time Server.

Configure Native OTP using the GUI

The native OTP registration is not just a single factor authentication. The following sections help you to configure the single and second factor authentication.

Create Login Schema for the first factor

  1. Navigate to Security > AAA-Application Traffic > Login Schema.
  2. Go to Profiles and click Add.
  3. On the Create Authentication Login Schema page, enter lschema_single_auth_manage_otp under the Name field and click the edit icon next to noschema.
  4. Click the LoginSchema folder.
  5. Scroll down to select SingleAuthManageOTP.xml and click Select.
  6. Click Create.
  7. Click Policies and Click Add.

  8. On the Create Authentication Login Schema Policy screen, enter the following values.

    Name: lpol_single_auth_manage_otp_by_url

    Profile: Select lschema_single_auth_manage_otp from the list.

    Rule: HTTP.REQ.COOKIE.VALUE("NSC_TASS").EQ("manageotp")

Configure authentication, authorization, and auditing virtual server

  1. Navigate to Security > AAA – Application Traffic > Authentication Virtual Servers. Click to edit the existing virtual server. For more information, see Authentication virtual server

  2. Click the + icon next to Login Schemas under Advanced Settings in the right pane.
  3. Select No Login Schema.
  4. Click the arrow and select the lpol_single_auth_manage_otp_by_url Policy, click Select, and click Bind.
  5. Scroll up and select 1 Authentication Policy under Advanced Authentication Policy.
  6. Right-click the nFactor Policy and select Edit Binding. Right-click the already configured nFactor Policy or refer to nFactor to create one and select Edit Binding.
  7. Click the arrow under Select Next Factor to select an existing configuration or click Add to create a factor.

  8. On the Create Authentication PolicyLabel screen, enter the following, and click Continue:

    Name: manage_otp_flow_label

    Login Schema: Lschema_Int

  9. On the Authentication PolicyLabel screen, click Add to create a Policy.

    Create a policy for a normal LDAP server.

  10. On the Create Authentication Policy screen, enter the following:

    Name: auth_pol_ldap_native_otp

  11. Select the Action type as LDAP using the Action Type list.

  12. In the Action field, click Add to create an action.

    Create the first LDAP action with authentication enabled to be used for single factor.

  13. In the Create Authentication LDAP server page, select the Server IP radio button, enter the following values, and select Test Connection. The following is a sample configuration.

    Name: ldap_native_otp

    IP Address: 192.8.xx.xx

    Base DN: DC=training, DC=lab

    Administrator: Administrator@training.lab

    Password: xxxxx

    Create a policy for OTP .

  14. On the Create Authentication Policy screen, enter the following:

    Name: auth_pol_ldap_otp_action

  15. Select the Action type as LDAP using the Action Type list.

  16. In the Action field, click Add to create an action.

    Create the second LDAP action to set OTP authenticator with OTP secret configuration and authentication unchecked.

  17. In the Create Authentication LDAP server page, select the Server IP radio button, clear the checkbox next to Authentication, enter the following values, and select Test Connection. The following is a sample configuration.

    Name: ldap_otp_action

    IP Address: 192.8.xx.xx

    Base DN: DC=training, DC=lab

    Administrator: Administrator@training.lab

    Password: xxxxx

  18. Scroll down to the Other Settings section. Use the drop-down menu to select the following options. Server Logon Name Attribute as New and type userprincipalname.
  19. Use the drop-down menu to select SSO Name Attribute as New and type userprincipalname.
  20. Enter “UserParameters” in the OTP Secret field and click More.

  21. Enter the following Attributes.

    Attribute 1 = mail Attribute 2 = objectGUID Attribute 3 = immutableID

  22. Click OK.
  23. On the Create Authentication Policy page, set the Expression to true and click Create.
  24. On the Create Authentication Policylabel page, click Bind, and click Done.
  25. On the Policy Binding page, click Bind.

  26. On the Authentication policy page, click Close and click Done.

    Create OTP for OTP verification.

  27. On the Create Authentication Policy screen, enter the following:

    Name: auth_pol_ldap_otp_verify

  28. Select the Action type as LDAP using the Action Type list.

  29. In the Action field, click Add to create an action.

    Create the third LDAP action to verify OTP.

  30. In the Create Authentication LDAP server page, select the Server IP radio button, clear the checkbox next to Authentication, enter the following values, and select Test Connection. The following is a sample configuration.

    Name: ldap_verify_otp

    IP Address: 192.168.xx.xx

    Base DN: DC=training, DC=lab

    Administrator: Administrator@training.lab

    Password: xxxxx

  31. Scroll down to the Other Settings section. Use the drop-down menu to select the following options. Server Logon Name Attribute as New and type userprincipalname.
  32. Use the drop-down menu to select SSO Name Attribute as New and type userprincipalname.
  33. Enter “UserParameters” in the OTP Secret field and click More.

  34. Enter the following Attributes.

    Attribute 1 = mail Attribute 2 = objectGUID Attribute 3 = immutableID

  35. Click OK.
  36. On the Create Authentication Policy page, set the Expression to true and click Create.
  37. On the Create Authentication Policylabel page, click Bind, and click Done.
  38. On the Policy Binding page, click Bind.
  39. On the Authentication policy page, click Close and click Done.

You probably don’t already have an Advanced Authentication Policy for your normal LDAP server. Change the Action Type to LDAP. Select your normal LDAP server, which is the one that has Authentication enabled. Enter true as the expression. This uses Advanced policy instead of Classic Syntax. Click Create.

Note:

The authentication virtual server must be bound to the RFWebUI portal theme. Bind a server certificate to the server. The server IP ‘1.2.3.5’ must have a corresponding FQDN that is, otpauth.server.com, for later use.

Create login schema for second factor OTP

  1. Navigate to Security > AAA-Application Traffic > Virtual Servers. Select the virtual server to be edited.
  2. Scroll down and select 1 Login Schema.
  3. Click Add Binding.
  4. Under the Policy Binding section, click Add to add a policy.
  5. On the Create Authentication Login Schema Policy page, enter the name of the policy, and click Add.
  6. On the Create Authentication Login Schema page, enter the name of the login schema and click the pencil icon next to noschema.
  7. Click the LoginSchema folder, select DualAuthManageOTP.xml, and then click Select.
  8. Click More and scroll down.
  9. In the Password Credential Index field, enter 1. This causes nFactor to save the user’s password into authentication, authorization, and auditing Attribute #1, which can be used later in a Traffic Policy to single sign-on to StoreFront. If you don’t do this, then NetScaler Gateway tries to use the Passcode to authenticate to StoreFront, which does not work.
  10. Click Create.
  11. In the Rule section, enter True. Click Create.
  12. Click Bind.
  13. Notice the two factors of authentication. Click Close and click Done.

Traffic Policy for single sign-on

  1. Navigate to NetScaler Gateway > Policies > Traffic
  2. On the Traffic Profiles tab, click Add.
  3. Enter a name for the traffic profile.

  4. Scroll down in the SSO Password Expression box, enter the following, and click Create. This is where we use the login schema password attribute specified for the second factor OTP.

    AAA.USER.ATTRIBUTE(1)

  5. On the Traffic Policies tab, click Add.

  6. In the Name field, enter a name for the traffic policy.

  7. In the Request Profile field, select the traffic profile you created.

  8. In the Expression box, enter True. If your NetScaler Gateway virtual server allows full VPN, change the expression to the following.

    http.req.method.eq(post)||http.req.method.eq(get) && false

  9. Click Create.

  10. Bind the traffic policy to a VPN virtual server.

    • Navigate to Security > AAA - Application Traffic > Authentication Profile.
    • Configure the authentication profile by selecting the NetScaler Gateway virtual server and then click OK.
    • Navigate to NetScaler Gateway > NetScaler Gateway Virtual Servers and select the NetScaler Gateway virtual server. The VPN Virtual Server page appears.
    • In the Policies section, click the + icon.
    • Select the policy type as Traffic and click Continue.
    • Select the traffic policy and click Bind.
    • Click Done.

Configure content switching policy for manage OTP

The following configurations are required if you are using Unified Gateway.

  1. Navigate to Traffic Management > Content Switching > Policies. Select the content switching policy, right click, and select Edit.

  2. Edit the expression to evaluate the following OR statement and click OK:

    is_vpn_url || HTTP.REQ.URL.CONTAINS("manageotp")

Configure Native OTP using the CLI

You must have the following information to configure the OTP device management page:

  • IP assigned to authentication virtual server
  • FQDN corresponding to the assigned IP
  • Server certificate for authentication virtual server

Note:

Native OTP is a web-based solution only.

To configure the OTP device registration and management page

Create authentication virtual server

add authentication vserver authvs SSL 1.2.3.5 443

bind authentication vserver authvs -portaltheme RFWebUI

bind ssl vserver authvs -certkeyname otpauthcert
<!--NeedCopy-->

Note:

The authentication virtual server must be bound to the RFWebUI portal theme. Bind a server certificate to the server. The server IP ‘1.2.3.5’ must have a corresponding FQDN that is, otpauth.server.com, for later use.

To create LDAP logon action 

add authentication ldapAction <LDAP ACTION NAME> -serverIP <SERVER IP> -  serverPort <SERVER PORT> -ldapBase <BASE> -ldapBindDn <AD USER> -ldapBindDnPassword <PASSWO> -ldapLoginName <USER FORMAT>

Example:

add authentication ldapAction ldap_logon_action -serverIP 1.2.3.4 -serverPort 636 -ldapBase "OU=Users,DC=server,DC=com" -ldapBindDn administrator@ctxnsdev.com -ldapBindDnPassword PASSWORD -ldapLoginName userprincipalname

To add authentication policy for LDAP Logon 

add authentication Policy auth_pol_ldap_logon -rule true -action ldap_logon_action

To present UI via LoginSchema

Show the user name field and password field to users upon logon

add authentication loginSchema lschema_single_auth_manage_otp -authenticationSchema "/nsconfig/loginschema/LoginSchema/SingleAuthManageOTP.xml"

Display device registration and management page

We recommend two ways of displaying the device registration and management screen: URL or host name.

Note:

  • Currently, device registration and device management can be performed only using a browser.

  • For management OTP or native OTP device registration to function, the loginschema with manageotp must be configured as the last factor requiring user input.

  • Using URL

    When the URL contains ‘/manageotp’

    • add authentication loginSchemaPolicy lpol_single_auth_manage_otp_by_url -rule 'http.req.cookie.value("NSC_TASS").contains("manageotp")' -action lschema_single_auth_manage_otp
    • bind authentication vserver authvs -policy lpol_single_auth_manage_otp_by_url -priority 10 -gotoPriorityExpression END

  • Using hostname

    When the host name is ‘alt.server.com’

    • add authentication loginSchemaPolicy lpol_single_auth_manage_otp_by_host -rule 'http.req.header("host").eq("alt.server.com")' -action lschema_single_auth_manage_otp
    • bind authentication vserver authvs -policy lpol_single_auth_manage_otp_by_host -priority 20 -gotoPriorityExpression END

To configure the user login page using the CLI

You must have the following information to configure the User Logon page:

  • IP for a load balancing virtual server
  • Corresponding FQDN for the load balancing virtual server

  • Server certificate for the load balancing virtual server

     bind ssl virtual server lbvs_https -certkeyname lbvs_server_cert

Back-end service in load balancing is represented as follows:

add service iis_backendsso_server_com 1.2.3.210 HTTP 80

bind lb vserver lbvs_https iis_backendsso_server_com

To create OTP passcode validation action 

add authentication ldapAction <LDAP ACTION NAME> -serverIP <SERVER IP> -serverPort <SERVER PORT> -ldapBase <BASE> -ldapBindDn <AD USER> -ldapBindDnPassword <PASSWORD> -ldapLoginName <USER FORMAT> -authentication DISABLED -OTPSecret <LDAP ATTRIBUTE>`

Example:

add authentication ldapAction ldap_otp_action -serverIP 1.2.3.4 -serverPort 636 -ldapBase "OU=Users,DC=server,DC=com" -ldapBindDn administrator@ctxnsdev.com -ldapBindDnPassword PASSWORD -ldapLoginName userprincipalname -authentication DISABLED -OTPSecret userParameters

Important:

The difference between the LDAP logon and OTP action is the need to disable the authentication and introduce a new parameter OTPSecret. Do not use the AD attribute value.

To add authentication policy for OTP passcode validation 

add authentication Policy auth_pol_otp_validation -rule true -action ldap_otp_action

To present the two-factor authentication through LoginSchema

Add the UI for two factor authentication.

add authentication loginSchema lscheme_dual_factor -authenticationSchema "/nsconfig/loginschema/LoginSchema/DualAuth.xml"
add authentication loginSchemaPolicy lpol_dual_factor -rule true -action lscheme_dual_factor

To create passcode validation factor via the policy label

Create a manage OTP flow policy label for the next factor (the first factor is LDAP logon)

add authentication loginSchema lschema_noschema -authenticationSchema noschema
add authentication policylabel manage_otp_flow_label -loginSchema lschema_noschema

To bind the OTP policy to the policy label 

bind authentication policylabel manage_otp_flow_label -policyName  auth_pol_otp_validation -priority 10 -gotoPriorityExpression NEXT

To bind the UI flow

Bind the LDAP logon followed by the OTP validation with the authentication virtual server.

bind authentication vserver authvs -policy auth_pol_ldap_logon -priority 10 -nextFactor  manage_otp_flow_label -gotoPriorityExpression NEXT
bind authentication vserver authvs -policy lpol_dual_factor -priority 30 -gotoPriorityExpression END

To create a traffic policy for single sign-on and bind it to a VPN virtual server 

add vpn trafficAction vpn_html_pol http -userExpression aaa.user.attribute(1) -passwdExpression aaa.user.attribute(2)

add vpn trafficpolicy tf1 'http.req.method.eq\(post)\||http.req.method.eq\(get) && false' vpn\_html\_pol

bind vpn vserver vpn1 -policy tf1 -priority 10

Register your device with NetScaler

Note:

The device registration is supported using a browser.

  1. On your browser, navigate to your NetScaler FQDN (first public facing IP), with a /manageotp suffix. For example, https://otpauth.server.com/manageotp Login with user credentials.

  2. Click the + icon to add a device.

    Gateway logon page

  3. Enter a device name and press Go. A barcode appears on the screen.
  4. Click Begin Setup and then click Scan Barcode.

  5. Hover the device camera over the QR code. You can optionally enter the code.

    QR code

    Note:

    The displayed QR code is valid for 3 minutes.

  6. Upon a successful scan, you are presented with a 6 digit time sensitive code that can be used to log in.

    Logon success message

  7. To test, click Done on the QR screen, then click the green check mark on the right.
  8. Select your device from the drop-down menu and enter the code from Google Authenticator (must be blue, not red) and click Go.
  9. Make sure to log out using the drop-down menu at the top right corner of the page.

Log in to NetScaler using the OTP

  1. Navigate to your first public-facing URL and enter your OTP from Google Authenticator to log on.

  2. Authenticate to the NetScaler splash page.

    ADC authentication page

Native OTP support for authentication
November 18, 2025
Contributed by: 
C
November 18, 2025
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.