Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cannot login after update from 3.5.1 to 3.6.1 #13678

Closed
fungiboletus opened this issue Nov 7, 2018 · 9 comments
Closed

Cannot login after update from 3.5.1 to 3.6.1 #13678

fungiboletus opened this issue Nov 7, 2018 · 9 comments
Labels
worksforme The issue cannot be reproduced and things work as intended.

Comments

@fungiboletus
Copy link

A correct login/password redirects to the login page with a 302 HTTP code. No errors and no login.

The installation is a bit special, using AWS ECS (I know) and an AWS load balancer as HTTPS reverse proxy. The proxy does not support X-Forwarded-Host headers or similar, but it used to work.

[General]
assume_secure_protocol = 1
enable_trusted_host_check = 0
@tsteur
Copy link
Member

tsteur commented Nov 7, 2018

Sorry I'm not quite understanding where the problem is. You log in, but nothing happens?

From which version did you update?

@fungiboletus
Copy link
Author

fungiboletus commented Nov 7, 2018 via email

@tsteur
Copy link
Member

tsteur commented Nov 7, 2018

Is the proxy maybe configured to forward the previous cookie name but not the new cookie name (I think the cookie name changed but not sure)

@fdellwing
Copy link
Contributor

Just a guess: Did you update to Firefox 63 at the same time the problem started appearing?

@fungiboletus
Copy link
Author

The proxy is configured to forward everything, it might have an issue though. I'm testing with various browsers without privacy extensions turned on.

After a successfull login, $_COOKIE looks like this:

Array
(
    [piwik_auth] => login=abcdef=:token_auth=abcdef==:_=abcdef
    [PIWIK_SESSID] => abcdef
)

So I guess the I was wrong, the cookie is correctly sent by the browser.

@fungiboletus fungiboletus changed the title Cannot login since 3.6.1 Cannot login after update from 3.5.1 to 3.6.1 Nov 8, 2018
@fungiboletus
Copy link
Author

I tried to debug more, but I think it's related to #12208 and I'm giving up. This new secure session stuff feels a bit too complicated to me.

I understand it's good security practice to fail without error messages, but it's frustrating. I have no idea where the problem is and the code base is too complex to debug for external people.

I'm available if you need more information.

@fungiboletus
Copy link
Author

Well, my bad. The cookie was set correctly but the session fingerprint wasn't initialised because the Login plugin wasn't updated to 3.6.1. I updated the plugin and now it works. It also explain the lack of error messages, it was a weird configuration (3.6.1 core and 3.5.1 login plugin).

Cheers.

@tsteur tsteur added the worksforme The issue cannot be reproduced and things work as intended. label Nov 8, 2018
@tsteur
Copy link
Member

tsteur commented Nov 8, 2018

Cheers for letting us know

@Meuk
Copy link

Meuk commented Nov 19, 2018

Hi Guys,

Sadly, I am running into the same problem. Last week I had this exact same problem with 3.6.3 running on a kubernetes cluster using a copy of the docker images provides in the matomo-docker repository. I am storing the sessions in Redis, the PIWIK session shows up in redis and is the same ID as the one in my cookie. Still I am getting redirected to the login page after succesful login.

Is there a way to figure out what versions of plugins I am using without access to the admin panel?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@fungiboletus @Meuk @tsteur @fdellwing