Login/registration broken in localdev

[ehirsch]

I have been following the documentation to setup a local wicked. Everything works like a charm! Until - I try to login.

Any attempt to login with the default admin user will result in the login page being shown again. When navigation away from the login page I am actually login. But now it is not possible to logout again…

Something is terrible off. (It all worked yesterday - I just recreated the setup step by step).

I am using the 'latest' tag so 0.11.6 is probably the version.

OS: macOS (10.12.5)
Browser: Chrome and Safari both current (59.0.3071.86 and 10.1.1)

[DonMartin76]

I can reproduce this on macOS 10.12 currently. I can't yet tell exactly what's wrong, will come back with more information as soon as I know more. It may have to do with the self signed certificates. Can you please also add operating system and the browser (and version) you are using?

Thanks for reporting!

[DonMartin76]

Everything works as intended when using (a) real DNS names, and (b) valid certificates (e.g. from Let's Encrypt, see https://wicked-demo.haufe.io), so this has either something to do with the certificates, or some DNS lookup hiccup when using /etc/hosts.

[achwie]

I've encountered a similar problem to Eike. For me the login didn't work randomly, but could be "fixed" by restarting the portal / portal-api services. Therefore to me it doesn't look like a config/cert issue.

[ehirsch]

Any new insights? Can I help with anything?

[achwie]

It seems like the user is authenticated correctly by the portal-api service. But somehow the auth info (user) is not transferred to the signup page during the success redirect to /signup (in passport/lib/authenticate.js:241). As far as I understand, this leads to the signup page not seeing the user as authenticated, because it expects the user object in the request but it's not there.

[DonMartin76]

I have actually found the culprit. It's the update of write-file-atomic from 1.3.1 to 1.3.4 which seems to have broken it (end of April/beginning of May). I will pin it to 1.3.1 for the time being and notify the maintainer of session-file-storage to do something about it.

[ehirsch]

Oh boy - the joy of the node ecosystem…
Good catch thou!

[DonMartin76]

Fixed in 0.11.7.