Private key problems
# troubleshooting
j
Hi all! I observed the same behavior after restarting my docker container (after docker compose modifications). Every time I have to delete the admin user and restart the container to regain access. Once I do that and set back the exact same password as before for the users I know, I can notice that in the db, the password hash changes
n
Have you tried setting the private key with a seed instead of a path to a file?
j
Not sure if related but every time i restart my container my session is broken. I found however that the logout function still works, so i do that and then log back in and all is fine.
n
Weird. Is the jwt secret changing by any chance?
j
No not changing the jwt secret
I get an error, can recreate in a couple of hours if you want
n
What do you mean by "my session is broken"?
j
It’s like the session expires
n
You can maybe give me the network calls from the page (F12 then refresh, network tab)
And you're not clearing first-party cookies?
j
sorry just tried to recreate and can't
tried recreating the containers and couldn't reproduce
maybe its when i destroy the local data (which is reasonable to break the session i'd say)
nope even destroying local data isn't doing it
maybe something else was actually causing it
Looks like this issue can be resolved in LibreNMS without any lldap changes
removing 4 x cast to int makes everything work
n
I might punt on the uidnumber feature, then, and if people need it later they can add them manually with user-defined attributes
Also, wrong thread 😅
j
hahaha
sorry thread