268674 - Logon to our Company-Website does not work - Memory Cookie not accepted

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Hans-Conrad Stamm]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0

Our company has a website www.crew.swiss.com which requires a logon. The Logon
goes via a seperate Notes-LDAP-Server which is done on awp.atraxis.com. 

Is the access is granted, a memory cookied is saved at the actual browser
session.  Only with this memory cookie (which is not written to any disk) the
logon completes. With IE this works, but with FireFox not. After Logon, for a
second the portal page is displayed, but after less than a secound the user will
be redirectes to the logonpage. This is because each page on the website checks
if the memory cookie is stored in the actual browser session.

Changing all the cookie-settings did not help.

I guess there is something wrong with memory cookies in Firefox. It looks the
memcookie is not stored properly.

Thanks for fixing this.



Reproducible: Always
Steps to Reproduce:
1. call www.crew.swiss.com
2. logon with corred Userid/pw
3. logon is ok, but after a secound user is redirected to logonpage

Actual Results:  
see text above

Expected Results:  
Normal logon. After logon, every call to a page on our company-website the
memory cookie (which is set after logon) is checked. Firefox has no sucess here,
the check fails.

Comment 1

[Jesse Ruderman]

Not being able to log into a web site is not a security hole.

Comment 2

[Daniel Veditz [:dveditz]]

possible dupe of bug 263057. flip the browser.chrome.favicons pref to false and
see if the problem goes away (no UI for it, use about:config)

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[Gervase Markham [:gerv]]

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.