-
Basic components of authentication, authorization, and auditing configuration
-
-
Native OTP support for authentication
-
Store OTP secret data in an encrypted format
-
Recommended native OTP configurations for device registration
-
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing with commonly used protocols
-
Troubleshoot authentication and authorization related issues
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Store OTP secret data in an encrypted format
Starting from NetScaler release 13.0 build 41.20, the OTP secret data can be stored in an encrypted format instead of plain text.
Previously, the NetScaler appliance stored OTP secret as a plain text in AD. Storing OTP secret in plain text poses a security threat as a malicious attacker or an admin might exploit the data by viewing the shared secret of other users.
The encryption parameter enables encryption of OTP secret in AD. When you register a new device with NetScaler version 13.0 build 41.20, and enable the encryption parameter, the OTP secret is stored in an encrypted format, by default. However, if the encryption parameter is disabled, the OTP secret is stored in plain text format.
For devices registered prior to 13.0 build 41.20, you must perform the following as a best practice:
- Upgrade the 13.0 NetScaler appliance to 13.0 build 41.20.
- Enable the encryption parameter on the appliance.
- Use the OTP secret migration tool to migrate OTP secret data from plain text format to encrypted format.
For details about the OTP secret migration tool, see OTP encryption tool.
Important
Citrix recommends you as an admin to ensure the following criteria is met:
A new certificate must be configured to encrypt OTP secrets if you are not using KBA as part of self-service password reset feature.
To bind the certificate to VPN global, you can use the following command:
bind vpn global -userDataEncryptionKey <certificate name>
If you are already using a certificate to encrypt KBA, you can use the same certificate to encrypt OTP secrets.
New OTP registrations always happen with the last bound certificate, as it gets the highest priority. In the example shown below, if you bind a certificate (cert1) and then bind another certificate (cert2), then cert2 is considered for device registration. If the certificate required for device registration is missing, the end user login fails.
bind vpn global -userDataEncryptionKey otp-cert1 bind vpn global -userDataEncryptionKey otp-cert2 <!--NeedCopy-->
In the following example, the
cert2
certificate is displayed as the first entry on the output of theshow vpn global
command:show vpn global Portal Theme: RfWebUI Userdata Encryption Certificate: cert2 Userdata Encryption Certificate: cert1 1) VPN Clientless Access Policy Name: ns_cvpn_owa_policy Priority: 95000 Bindpoint: REQ_DEFAULT 2) VPN Clientless Access Policy Name: ns_cvpn_sp_policy Priority: 96000 Bindpoint: REQ_DEFAULT 3) VPN Clientless Access Policy Name: ns_cvpn_sp2013_policy Priority: 97000 Bindpoint: REQ_DEFAULT 4) VPN Clientless Access Policy Name: ns_cvpn_default_policy Priority: 100000 Bindpoint: REQ_DEFAULT <!--NeedCopy-->
To enable OTP encryption data by using the CLI
At the command prompt, type:
set aaa otpparameter [-encryption ( ON | OFF )]
Example
set aaa otpparameter -encryption ON
To configure the OTP encryption by using the GUI
- Navigate to Security > AAA – Application Traffic and click Change authentication AAA OTP Parameter under Authentication Settings section.
- On the Configure AAA OTP Parameter page, select OTP Secret encryption.
- Click OK.
Configuring the number of end-user devices for receiving OTP notifications
Administrators can now configure the number of devices that an end user can register to receive OTP notification or authentication.
To configure the number of devices in OTP by using the CLI
At the command prompt, type:
set aaa otpparameter [-maxOTPDevices <positive_integer>]
Example
set aaa otpparameter -maxOTPDevices 4
To configure the number of devices by using the GUI
-
Navigate to Security > AAA – Application Traffic.
-
In the Authentication Settings section, click Change authentication AAA OTP Parameter.
-
On the Configure AAA OTP Parameter page, enter the value for Max OTP device Configured.
-
Click OK.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.