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!
Client certificate authentication using advanced policies
Following are the steps to configure client certificate authentication on Citrix ADC using advanced policies.
- Navigate to Security > AAA - Application Traffic > Virtual Servers.
-
In the details pane, select the virtual server that you want to configure to handle client certificate authentication, and click Edit.
Note:
If you have imported a valid CA certificate and server certificate for the virtual server you can skip step 3 to step 10.
- On the Configuration page, under Certificates, click > to open the CA Cert Key installation dialog box.
- In the CA Cert Key dialog box, click Insert.
- In the CA Cert Key - SSL Certificates dialog box, click Install.
-
In the Install Certificate dialog box, set the following parameters, whose names correspond to the CLI parameter names as shown:
- Certificate-Key Pair Name—certkeyName
- Certificate File Name—certFile
- Key File Name—keyFile
- Certificate Format—inform
- Password—password
- Certificate Bundle—bundle
- Notify When Expires—expiryMonitor
- Notification Period—notificationPeriod
- Click Install, and then click Close.
- In the CA Cert Key dialog box, from the Certificate list, select the root certificate.
- Click Save.
- Click Back to return to the main configuration screen.
- Navigate to Security > AAA - Application Traffic > Policies > Authentication > Advanced Policies, and then select Policy.
-
In the details pane do one of the following:
- To create a new policy, click Add.
- To modify an existing policy, select the policy, and then click Edit.
-
In the Create Authentication Policy or Configure Authentication Policy dialog box, type or select values for the parameters.
- Name - The policy name. Cannot be changed for a previously configured policy.
- Action Type - Select Cert
- Action - The authentication action (profile) to associate with the policy. You can choose an existing authentication action, or click the plus and create a new action of the proper type.
- Log Action - The audit action to associate with the policy. You can choose an existing audit action, or click the plus and create a new action.
- Expression - The rule that selects connections to which you want to apply the action that you specified. The rule can be simple (“true” selects all traffic) or complex. You enter expressions by first choosing the type of expression in the leftmost drop-down list beneath the Expression window, and then by typing your expression directly into the expression text area, or by clicking Add to open Add Expression dialog box and using the drop-down lists in it to construct your expression.)
- Comment - You can type a comment that describes the type of traffic that this authentication policy will apply to. Optional.
- Click Create or OK, and then click Close. If you created a policy, that policy appears in the Authentication Policies and Servers page.
Share
Share
In this article
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.