Commented Feature: [WebAPI] No way to access SSL client certificate [31]

The title says it all.

There are certainly ways to do hosting specific tricks - but the concept of client certs should be baked into Web API itself. This is important for security scenarios.

From an OM point of view this logically belongs on HttpRequestMessage (in one or the other way).
Comments: I played with the sample. I changed it so the client cert/signing is obtained from a .pfx file rather than a cert store. the SSL server is registered per the sample, with a kernel-managed https. is it really an SSL client cert (i.e. layer 4 in the ssl handshake) Or is it a layer 7 client cert - as used in the likes of a ws-trust handshake this is very relevant to me. Every other server-side project on windows that has promised to process SSL-layer4 client certs has only released the client cert to user space processes ONLY AFTER one has managed the server and pre-registered the client cert (or its root cert) in a cert store. This was never necessary for wcf/layer7 certs, which are not processed using https.sys mechanisms in the kernel.