Update description of Application Gateway mTLS auth server variable client_certificate_verification#128589
Conversation
…client_certificate_verification` Update description of Application Gateway mTLS auth server variable `client_certificate_verification` based on the behaviour I've observed (Standard_v2 AGW): - Passthrough mode: - NONE when no certificate is presented - PASSTHROUGH if a certificate is presented - Strict mode - SUCCESS when certificate is valid - Empty when certificate is invalid
|
@ronaldbosma : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
1 similar comment
|
@ronaldbosma : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 56d09fa: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the documentation for the Application Gateway mTLS auth server variable client_certificate_verification to reflect observed outputs in passthrough vs strict modes (notably for Standard_v2).
Changes:
- Revised the
client_certificate_verificationserver-variable description to enumerate values by mTLS mode. - Documented that strict mode may return an empty value when the client certificate is invalid (per observed behavior).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Clarified the description of client_certificate_verification for mTLS modes base on Copilot suggestions
|
Learn Build status updates of commit ab165a3: ✅ Validation status: passed
For more details, please refer to the build report. |
|
#assign-reviewer: @JackStromberg |
|
#unassign-reviewer: @JackStromberg |
Update description of Application Gateway mTLS auth server variable
client_certificate_verificationbased on the behaviour I've observed (Standard_v2 AGW):