Adds client certificate authentication support #610
Merged
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.
Description of the Change
Adds client certificate authentication support, as well as just generally allowing client certificates to be sent on requests and retrieved.
There's a new
-AllowClientCertificate
switch onAdd-PodeEndpoint
for HTTPS endpoints. When supplied, any requests to the server will accept a client certificate to be sent. This certificate is then available in theRequest
object underClientCertificate
, which is accessible from the current web event.There's also a new
-ClientCertificate
switch onNew-PodeAuthScheme
; the appropriate scriptblock fromAdd-PodeAuth
will be supplied with the client's certificate and any errors.Related Issue
Resolves #472
Examples
By default, Pode will validate the certificate is present, and the Before/After dates - if not valid a 401 response is returned.