-
Integrate the Citrix Secure Access client with Citrix Workspace app
-
Enforce the HttpOnly flag on authentication cookies
-
Configure connections for the Citrix Secure Access client
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!
Enforce the HttpOnly flag on authentication cookies
Starting from NetScaler Gateway release 13.1-37.x and later, the HttpOnly flag is available on the authentication cookies of VPN scenarios that is, NSC_AAAC and NSC_TMAS cookies. The NSC_TMAS authentication cookie is used during the nFactor authentication and the NSC_AAAC cookie is used for the authenticated session. The HttpOnly flag on a cookie restricts the cookie access using the JavaScript document cookie option. This helps in preventing cookie theft because of cross-site scripting.
Starting from Citrix Secure Access for Windows 24.8.1.x and NetScaler Gateway 14.1-34.x, the home page of Citrix Secure Access client launches successfully with HttpOnly cookie enabled on NetScaler Gateway. In the previous versions, when the HttpOnly feature was enabled, the Home page link on Citrix Secure Access client UI did not work.
Supported scenario
The HTTPOnly flag is supported for nFactor authentication.
Behavior when NetScaler AAA parameter’s HttpOnlyCookie knob is used along with Traffic Management (TM) session’s HttpOnlyCookie knob:
-
When the httpOnlyCookie knob is enabled for authentication, authorization, and auditing, it overrides the traffic management session’s HttpOnlyCookie knob during nFactor authentication. Also, both NSC_TMAS and NSC_AAAC are marked HttpOnly regardless of the session type. This applies whether it is a VPN session, TM session, or nFactor authentication.
-
If the HttpOnlyCookie knob is disabled, the HttpOnly flag is not set for a VPN session. For the authentication, authorization, and auditing scenario, the HttpOnly flag is set based on the TM session knob value.
Configure the HttpOnly feature by using the CLI
-
Enable the HttpOnly flag
set aaa parameter -httpOnlyCookie ENABLED <!--NeedCopy--> -
Check the status of the HttpOnly feature
show aaa parameter <!--NeedCopy-->
Limitations
- HttpOnly flag is not set in any classic authentication.
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.