Tickets :: Comment on [#1801] first time imp authentication error with hordeauth

* Your Email Address
* Spam protection	Enter the letters below: . ..__..__ ..__ \|\/\|\| \|[__) \|[__) \| \|\|__\|\| \__\|[__)
Comment	> Here's some additional information I've found with this: > > > > For us, its either a first-time or second-time authentication error > with IMP. One install, with IMP setup as the initial application, > displays my INBOX the first time, but I get an authentication error > when I click on a message to read it. Another install immediately > throws me into a redirect loop. > > > > If I stop the redirect loop, and have a mail summary block in my > portal view, I'm able to login successfully in the second looping > scenario. > > > > I've captured some packets in the first scenario, which seems to be > reproducible for the first login attempt, per browser session (i.e. > if I quit the browser and restart it, the first attempt to access a > message after logging in will fail. If I just logout and back in, I > don't have the problem). The username and password that is being > passed on the failed login is: kevin_myer {8}. > > > > We're using IU13 for $conf['session']['name']. > > > > For a failed login, the value of the cookie set for IU13 == the value > set for imp_key, and auth_key is different (this seems to be true for > all failed logins). Sometimes for a successful login, IU13 != > auth_key != imp_key. But sometimes, I think auth_key == imp_key too. > > > > imp_key remains the same, even after a logout. > > > > Should the cookie values be getting cleared after a successful logout > or only after the browser is closed? > > > > Going to see if I can figure out what different code path the mail > summary block takes for authentication, versus a traditional display > the INBOX and click on a message authentication...
Attachment
Watch this ticket

Saved Queries