Project

General

Profile

Actions

Bug #12489

closed

Cannot login into 2 different Rudder with the same URL - apocalypse ensues

Added by Raphael GAUTHIER about 6 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Security
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Large
Priority:
10
Name check:
Fix check:
Regression:

Description

Something (not so) funny happened.

I was working on my development platform (localhost/rudder), and I wanted to log in my test platform (localhost:8381/rudder). Once I logged in it, strange things started to happen...
I couldn't logout anymore from my dev platform, I got this error in my Eclise console:

WARN  net.liftweb.http.LiftRules - Unmapped Lift-like parameter seen in request [/lift/ajax/F1031420927474V324VA-00/]: F1031420927497KWOPVO

So I reloaded the page and fall back on the login form. And from there, I couldn't login anymore. Each times I tried, I got this error :

WARN  application - Login authentication failed for user 'unknown' from IP '127.0.0.1|X-Forwarded-For:::1': Maximum sessions of 2 for this principal exceeded

I tried to use private mode, or a different navigator, but the error persisted. The only way I found to be able to login again is to delete the browser cookies, then restart the Jetty server.

However, It works well if I use localhost/rudder for my dev platform and 192.168.XXX.XXX/rudder form my test platform.


Related issues 1 (1 open0 closed)

Related to Rudder - Architecture #16051: Re-authentication error in postgres doesn't kill existing poolNewActions
Actions

Also available in: Atom PDF