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!
Configure per-directory client authentication
If you create an action specifying client-side authentication on a per-directory basis, a client identified by a policy associated with the action is not authenticated as part of the initial SSL handshake. Instead, authentication is carried out every time the client wants to access a specific directory on the web server.
For example, if you have multiple divisions in the company, where each division has a folder in which all its files are stored, and you want to know the identity of each client that tries to access files from a particular directory, such as the finance directory, you can enable per-directory client authentication for that directory.
To enable per-directory client authentication, first configure client authentication as an SSL action, and then create a policy that identifies the directory that you want to monitor. When you create the policy, specify your client-authentication action as the action associated with the policy. Then, bind the policy to the SSL virtual server that will receive the SSL traffic.
Create an SSL action and a policy to enable client authentication by using the command line interface
At the command prompt, type the following commands to create an SSL action to enable to client authentication and verify the configuration:
add ssl action <name> [-clientAuth ( DOCLIENTAUTH | NOCLIENTAUTH )]
show ssl action [<name>]
add ssl policy <name> -rule <expression> [-action <string>] [-undefAction <string>] [-comment <string>]
show ssl policy [<name>]
<!--NeedCopy-->
Example:
add ssl action ssl-action-1 -clientAuth DOCLIENTAUTH
Done
show ssl action ssl-action-1
1) Name: ssl-action-1
Client Authentication Action: DOCLIENTAUTH
Hits: 0
Undef Hits: 0
Action Reference Count: 1
Done
add ssl policy ssl-pol-1 -rule 'REQ.HTTP.METHOD==GET' -reqaction ssl-action-1
sh ssl policy ssl-pol-1
Name: ssl-pol-1
Rule: REQ.HTTP.METHOD == GET
Action: ssl-action-1
UndefAction: Use Global
Hits: 0
Undef Hits: 0
Done
<!--NeedCopy-->
Create an SSL action to enable client authentication by using the GUI
- Navigate to Traffic Management > SSL > Policies and, on the Actions tab, click Add.
- In the Client Authentication list, select Enabled.
Create and bind an SSL policy to enable client authentication by using the GUI
-
Navigate to Traffic Management > SSL and, on the Polices tab, click Add.
-
Navigate to Traffic Management > Load Balancing > Virtual Servers and open an SSL virtual server.
-
In Advanced Settings, select SSL Policy, and bind the policy to the virtual server.
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.