No details on how to specify certificate store and location
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp
- Domain
- documentation
Research direction
Read aspnetcore/fundamentals/servers/kestrel/endpoints.md at the certificate configuration example and verify the documented Subject, Store, Location, and AllowInvalid values. Done when the page includes concrete examples or valid options for each key, especially for certificates in the Windows certificate store.
Written by the indexing model from the issue text.
Description
Description
When describing how to specify a certificate for use with Kestrel, the example below is given, but there are no details on how to format the Subject, or what values should be used for the Store and Location keys. A few examples, or list of all options would be helpful. Especially for common cases like using a cert in the Windows Cert store.
"Certificate": {
"Subject": "<subject; required>",
"Store": "<certificate store; required>",
"Location": "<location; defaults to CurrentUser>",
"AllowInvalid": "<true or false; defaults to false>"
}
Page URL
Content source URL
Document ID
fd9cc0c2-3ea3-f437-e0ac-8789fb96faf7
Platform Id
08b5cdab-b211-0993-3780-76cf77185dbc
Article author
@tdykstra
Metadata
- ID: 312df0ba-e769-c904-40b2-733c291704a0
- PlatformId: 08b5cdab-b211-0993-3780-76cf77185dbc
- Service: aspnet-core
- Sub-service: fundamentals
- Dominant language
- C#
- Stars
- 13.1k
- Forks
- 24.6k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 113
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/AspNetCore.Docs
-
:watch: Not Triaged 11.0 security/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
dotnet/AspNetCore.Docs#37710 ·
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dotnet/AspNetCore.Docs#37698 ·
-
11.0 SignalR
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
dotnet/AspNetCore.Docs#37694 ·
-
:watch: Not Triaged aspnet-core/svc security/subsvc Source - Docs.ms
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
dotnet/AspNetCore.Docs#37667 ·
All issues in dotnet/AspNetCore.Docs
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·