Authentication protocol error for Protocol error: This error results from an error during password verification``
#1078
-
|
Hello, I am using lldap as a server within my family. After updating my system (including update of lldap from My config is as follows: Environment variables: with (All secret values and domains are changed of course) After upgrading I first got this error: After removing the environment_file (which included only the LLDAP_KEY_SEED the error is gone, but I cannot login anymore. The error below is given. Also, I can see that the Can anyone help out what the problem might be? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Interesting failure mode :D That wasn't quite anticipated in the error message, and it mislead you (although it was technically correct). The recommendation from the error message (removing the key_seed) is only if you upgrade from 0.4 to 0.5+. You're upgrading from 0.5 to 0.6. That's the only other ambiguous case, since after that it's a hard error (as you have discovered). What you haven't seen is that in your logs before migrating, it was telling you that it was ignoring the key file and loading the seed instead. So the correct way to fix your installation is to put the key seed back in place and remove the key file (keep it around just in case, but rename it. Or even better, set the key_file config value to an empty string) |
Beta Was this translation helpful? Give feedback.
-
|
Ok, that indeed worked. Thanks. |
Beta Was this translation helpful? Give feedback.
Interesting failure mode :D That wasn't quite anticipated in the error message, and it mislead you (although it was technically correct).
The recommendation from the error message (removing the key_seed) is only if you upgrade from 0.4 to 0.5+. You're upgrading from 0.5 to 0.6. That's the only other ambiguous case, since after that it's a hard error (as you have discovered).
What you haven't seen is that in your logs before migrating, it was telling you that it was ignoring the key file and loading the seed instead. So the correct way to fix your installation is to put the key seed back in place and remove the key file (keep it around just in case, but rename it. Or even better, set the k…