Comment #120 on issue 318 by marcelo.dacruz: Client SSL Certificate Support
http://code.google.com/p/chromium/issues/detail?id=318
Ok, so I can confirm certificate generation is not working in Chrome (with
fake User-agent), using
Verisign's PIP (when changing User-agent to match Firefox's)
Steps to reproduce:
1) Follow steps 1-2 is comment 117 to create the account in Verisign's PIP
2) Make sure you don't have a PIP/Verisign certificate associated with your
browser: unbind the certificates that show up in PIP (just click
on "delete" on the certificate management section), and
delete the certificate from you keystore (use a Windows management console,
and attach the certificate
snap-in)
3) Start Chrome as explained by progame in comment 118
4) Follow step 3-4 in comment 117 to generate the certificate with Chrome
--> Remember that PIP won't let you login if you have certificate-based
authentication enabled and the
browser you are using is not binded to a cert: you'll have to let PIP send
an OTP to your e-mail account
and use that for a temporary login
Current behavior:
--> PIP will try to issue the cert requests, but will fail (no cert
generation request pops up in the
browser as it should).
Summing up:
1. Chrome grabbing the certificate from Window's keystore: Working
--> Includes certificates that have been generated by IE
2. Chrome generating a cert request, sending it to the web application, and
installing the resulting
certificate: Not working
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
