Light Freshness Edit: ASP.NET - Config Cert Auth#37064
Open
GitHubber17 wants to merge 5 commits intodotnet:mainfrom
Open
Light Freshness Edit: ASP.NET - Config Cert Auth#37064GitHubber17 wants to merge 5 commits intodotnet:mainfrom
GitHubber17 wants to merge 5 commits intodotnet:mainfrom
Conversation
Contributor
Author
|
Hi @blowdart - This PR contains light freshness edits for your review. See the top comment for details and issues to address. Thanks |
blowdart
requested changes
Apr 28, 2026
Contributor
Author
wadepickett
reviewed
Apr 29, 2026
| HttpSys has two settings that control the client certificate negotiation and both should be set. The first is in the _netsh.exe_ file under `http add sslcert clientcertnegotiation=enable/disable`. This flag indicates whether to negotiate the client certificate at the start of a connection. Set the value to `disable` for optional client certificates. For more information, see the `http add sslcert` parameter usage in the [netsh docs](/windows-server/administration/windows-commands/netsh-http#parameters). | ||
|
|
||
| The other setting is <xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.ClientCertificateMethod>. When set to `AllowRenegotation`, the client certificate can be renegotiated during a request. | ||
| The other setting is the <xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.ClientCertificateMethod> method. When set to `AllowRenegotation`, the client certificate can be renegotiated during a request. |
Contributor
There was a problem hiding this comment.
Suggested change
| The other setting is the <xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.ClientCertificateMethod> method. When set to `AllowRenegotation`, the client certificate can be renegotiated during a request. | |
| The other setting is the <xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.ClientCertificateMethod> property. When set to `AllowRenegotation`, the client certificate can be renegotiated during a request. |
ClientCertificateMethod is a property on HttpSysOptions, not a method.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains light freshness updates to the following article:
Configure certificate authentication in ASP.NET Core
moniker range=">= aspnetcore-6.0"onlyShould the article target a different issue, or the reference be removed?
For details, see ADO request 568764.
Internal previews