[GH-ISSUE #848] [BUG] error: Invalid JWT #307

New issue

Closed

opened 2026-02-27 08:16:33 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 08:16:33 +03:00

Owner

Originally created by @ryan2025 on GitHub (Feb 24, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/848

Describe the bug
Invalid JWT no if the secret is changed.

To Reproduce
After the container starts, going into the container reproduces the error.

Expected behavior
Expected to enter the gui interface and not be seen with any JWT issues.

Logs
WARNING: A key_seed was given, we will ignore the server_key and generate one from the seed!

Setup permissions..
Starting lldap..

Loading configuration from /data/lldap_config.toml
2024-02-24T12:28:12.648719467+00:00 INFO set_up_server [ 5.51ms | 100.00% ]
2024-02-24T12:28:12.648739883+00:00 INFO ┝━ ｉ [info]: Starting LLDAP version 0.5.1-alpha
2024-02-24T12:28:12.665632105+00:00 INFO ┝━ ｉ [info]: Starting the LDAP server on port 3890
2024-02-24T12:28:12.666258886+00:00 INFO ┕━ ｉ [info]: Starting the API/web server on port 17170
2024-02-24T12:28:12.666423589+00:00 INFO ｉ [info]: starting 1 workers
2024-02-24T12:28:12.666500349+00:00 INFO ｉ [info]: Actix runtime found; starting in Actix runtime
2024-02-24T12:28:12.667637826+00:00 INFO ｉ [info]: DB Cleanup Cron started
2024-02-24T12:28:42.665947827+00:00 INFO LDAP session [ 426µs | 44.93% / 100.00% ]
2024-02-24T12:28:42.666118552+00:00 INFO ┕━ LDAP request [ 234µs | 55.07% ]
2024-02-24T12:28:58.921913036+00:00 ERROR 🚨 [error]: | error: Invalid JWT
2024-02-24T12:28:58.923999669+00:00 ERROR 🚨 [error]: | error: Invalid JWT
2024-02-24T12:28:58.995623599+00:00 ERROR 🚨 [error]: | error: Invalid JWT
2024-02-24T12:29:12.753704871+00:00 INFO LDAP session [ 422µs | 43.82% / 100.00% ]
2024-02-24T12:29:12.753844558+00:00 INFO ┕━ LDAP request [ 237µs | 56.18% ]

Originally created by @ryan2025 on GitHub (Feb 24, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/848 **Describe the bug** Invalid JWT no if the secret is changed. **To Reproduce** After the container starts, going into the container reproduces the error. **Expected behavior** Expected to enter the gui interface and not be seen with any JWT issues. **Logs** WARNING: A key_seed was given, we will ignore the server_key and generate one from the seed! > Setup permissions.. > Starting lldap.. Loading configuration from /data/lldap_config.toml 2024-02-24T12:28:12.648719467+00:00 INFO set_up_server [ 5.51ms | 100.00% ] 2024-02-24T12:28:12.648739883+00:00 INFO ┝━ ｉ [info]: Starting LLDAP version 0.5.1-alpha 2024-02-24T12:28:12.665632105+00:00 INFO ┝━ ｉ [info]: Starting the LDAP server on port 3890 2024-02-24T12:28:12.666258886+00:00 INFO ┕━ ｉ [info]: Starting the API/web server on port 17170 2024-02-24T12:28:12.666423589+00:00 INFO ｉ [info]: starting 1 workers 2024-02-24T12:28:12.666500349+00:00 INFO ｉ [info]: Actix runtime found; starting in Actix runtime 2024-02-24T12:28:12.667637826+00:00 INFO ｉ [info]: DB Cleanup Cron started 2024-02-24T12:28:42.665947827+00:00 INFO LDAP session [ 426µs | 44.93% / 100.00% ] 2024-02-24T12:28:42.666118552+00:00 INFO ┕━ LDAP request [ 234µs | 55.07% ] 2024-02-24T12:28:58.921913036+00:00 ERROR 🚨 [error]: | error: Invalid JWT 2024-02-24T12:28:58.923999669+00:00 ERROR 🚨 [error]: | error: Invalid JWT 2024-02-24T12:28:58.995623599+00:00 ERROR 🚨 [error]: | error: Invalid JWT 2024-02-24T12:29:12.753704871+00:00 INFO LDAP session [ 422µs | 43.82% / 100.00% ] 2024-02-24T12:29:12.753844558+00:00 INFO ┕━ LDAP request [ 237µs | 56.18% ]

kerem

2026-02-27 08:16:33 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 08:16:34 +03:00

Author

Owner

@nitnelave commented on GitHub (Feb 24, 2024):

It's a bit hard to see what's going on, here. First things first: have you tried clearing your cookies? You might have a JWT coming from a previous setup.

If that doesn't work, I'll need some more info:

can you post the LLDAP logs after turning on the verbose mode?
what are you doing exactly to trigger the error? Opening the web UI? Trying to log in on the web UI?
have you ever changed your JWT secret environment variable for LLDAP? Maybe for a previous setup?

@nitnelave commented on GitHub (Feb 24, 2024): It's a bit hard to see what's going on, here. First things first: have you tried clearing your cookies? You might have a JWT coming from a previous setup. If that doesn't work, I'll need some more info: - can you post the LLDAP logs after turning on the verbose mode? - what are you doing exactly to trigger the error? Opening the web UI? Trying to log in on the web UI? - have you ever changed your JWT secret environment variable for LLDAP? Maybe for a previous setup?

kerem commented

2026-02-27 08:16:34 +03:00

Author

Owner

@ryan2025 commented on GitHub (Feb 25, 2024):

Oh man, I feel like such an idiot. Just had to clear my cookies... I thought I did that in the past but pretty sure I just cleared the browsing data.

@ryan2025 commented on GitHub (Feb 25, 2024): Oh man, I feel like such an idiot. Just had to clear my cookies... I thought I did that in the past but pretty sure I just cleared the browsing data.

kerem commented

2026-02-27 08:16:34 +03:00

Author

Owner

@ryan2025 commented on GitHub (Feb 25, 2024):

Solved after clearing cookies.

@ryan2025 commented on GitHub (Feb 25, 2024): Solved after clearing cookies.

kerem referenced this issue

2026-02-27 08:18:24 +03:00

[PR #307] [MERGED] server: Add support for PKCS1 keys #671