-
Notifications
You must be signed in to change notification settings - Fork 37
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
Login/registration broken in localdev #72
Comments
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! |
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 |
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. |
Any new insights? Can I help with anything? |
It seems like the user is authenticated correctly by the |
I have actually found the culprit. It's the update of |
…o version 1.3.1 for the time being (used by session-file-store). Additionally update some other components.
Oh boy - the joy of the node ecosystem… |
Fixed in 0.11.7. |
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)
The text was updated successfully, but these errors were encountered: