Specify the file which cannot be decrypted when invalid master key file error is raised
#481
Labels
feature
New feature
Comments
fluca1978
added a commit
to fluca1978/pgagroal
that referenced
this issue
Nov 4, 2024
When a users file, (frontend, admins or users files) cannot be decrypted, a generic `Invalid master key file` was raised. This commit adds the target file that cannot be decrypted, so that the user can understand which file has to be adjusted (e.g., `pgagroal-admin` usage on such file). Makes the error messages consistent with those about a missing file. Close agroal#481
fluca1978
added a commit
that referenced
this issue
Nov 4, 2024
When a users file, (frontend, admins or users files) cannot be decrypted, a generic `Invalid master key file` was raised. This commit adds the target file that cannot be decrypted, so that the user can understand which file has to be adjusted (e.g., `pgagroal-admin` usage on such file). Makes the error messages consistent with those about a missing file. Close #481
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When
pgagroalstarts, if it cannot decrypt axxx_users.conffile information, it raises theInvalid master key fileerror.This does not help in understand which file cannot be decrypted, hence it does not help in understanding which file has to be "adjusted" (via for example
pgagroal-admin).On the other hand, if one
xxx_users.conffile is not found, the error message clearly shows which file is missing.I propose to uniform the error messages, so that if a file cannot be decrypted, the error message (and optionally the systemd status message) includes the target file.
The text was updated successfully, but these errors were encountered: