dotnet/aspnetcore

ITlsConnectionFeature should include client certificate chain elements

Open

#2,708 opened on Jan 2, 2018

View on GitHub
 (10 comments) (1 reaction) (0 assignees)C# (10,653 forks)batch import
affected-very-fewarea-networkingenhancementfeature-http-abstractionshelp wantedseverity-minor

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

From @alextolp on Sunday, April 2, 2017 8:24:37 PM

It should be possible to access the client certificate and any chain elements that were presented by the client when the TLS connection was established. Currently the feature only exposes the client certificate, without any intermediate certificates, making it very difficult to work with the chain elements in the mvc layer.

Copied from original issue: aspnet/HttpAbstractions#808

Contributor guide

Research direction
Explore how the current ITlsConnectionFeature exposes the client certificate and investigate where the full certificate chain can be obtained from the underlying TLS stream. Then extend the feature to include a list of X509Certificate2 representing the chain.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40