User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Apache + OpenSSL, client + server certificates generated from the same CA, apache set to require client certificate and prompt for basic authentication. Client cert stored in Aladdin eTokin, browser correctly prompts for eToken password, shows server certificate, but does not prompt for basic authentication. Works fine without SSL, and works fine without basic auth, but the two together don't. Worked OK with 1.0. Reproducible: Always Steps to Reproduce: 1.Install apache + OpenSSL 2.Generate certificates, configure apache to require client cert 3.Create .htaccess file for apache and configure for basic authentication 4.Copy client cert to PC, fire up browser and point at apache server Actual Results: Client certificate accepted, server certificate displayed, no prompt for authentication, blank page. Expected Results: Prompted for basic auth. Client certificate stored in Aladdin eToken.
Rob, can you please generate a HTTP log using the steps described here: http://www.mozilla.org/projects/netlib/http/http-debugging.html thanks!
Emailed Darin direct with HTTP log file.
BASIC + SSL doesn't challenge for username/password even after closing all firebird instances.
Rob: could you please re-send the HTTP log to me (firstname.lastname@example.org). I don't have it in my inbox, and I suspect you may have sent it to email@example.com since that address was valid back in July. I no longer work for AOL.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.