Hi,
Has anybody had experience with multiple client certificates? Whenever
you hit a server and you have multiple certificates, a dialog pops up
asking which certificate to send. And every time HttpClient has to
create a new socket (SocketFactoryWrapper), the dialog pops up again.
In my tests, if the client doesn't hit the server for 20 seconds, it has
to create a new socket (keep-alive).
Is there any way around this behavior?
Is there a way to detect when the server is asking for the client
certificate, figure out which one the user selects, and next time the
server asks, send them the same one?
Is anybody using multiple client certificates and their app is not
behaving this way? Am I just doing something wrong?
Thanks.
--
Aloha,
Richard Suematsu
SynCaDD Systems, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
