Skip to content
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

ERROR: SCRAM authentication failed DETAIL: unable to decrypt password from pool_passwd HINT: verify the valid pool_key exists #72645

Closed
642070630 opened this issue Sep 20, 2024 · 3 comments
Assignees
Labels
pgpool solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@642070630
Copy link

642070630 commented Sep 20, 2024

Name and Version

bitname/pgpool all

What architecture are you using?

None

What steps will reproduce the bug?

Start the container as root, run the scram-sha-256 authentication command, and connect to pgpool through psql -h 127.0.0.1 -p 5432 -U postgres

What is the expected behavior?

When you run psql -h 127.0.0.1 -p 5432 -U postgres to connect to pgpool, the connection succeeds

What do you see instead?

The following message is displayed when you run psql -h 127.0.0.1 -p 5432 -U postgres to connect to pgpool

 ERROR: SCRAM authentication failed DETAIL: unable to decrypt password from pool_passwd HINT: verify the valid pool_key exists

Additional information

In the pgpool_generate_password_file function of libpgpool.sh, chmod 0600 "$PGPOOLKEYFILE" is used to set the permission for the key file to be too small. As a result, the key file cannot be read normally. If the authentication fails, you can set the permission of the KEY through "chmod 0644"

@642070630 642070630 added the tech-issues The user has a technical issue about an application label Sep 20, 2024
@github-actions github-actions bot added the triage Triage is needed label Sep 20, 2024
@carrodher
Copy link
Member

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Copy link

github-actions bot commented Oct 9, 2024

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Oct 9, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pgpool solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants