Dynamic client certificates without socket exhaustion
I have a server that is called by users passing in a representation of a client cert that is then used to call some dependent APIs using that client certs context.
HttpClientFactory doesn't seem to support dynamically supplying certificates without awareness of their existence prior to the call.
What would be the best practice to implement this to avoid socket exhaustion? Just looking for a point in the right directions.
HttpClientFactory doesn't seem to support dynamically supplying certificates without awareness of their existence prior to the call.
What would be the best practice to implement this to avoid socket exhaustion? Just looking for a point in the right directions.
