harbor: failed to create a new keydbstore: pq: unknown authentication response: 10

I’m using the Harbor Operator to deploy a harbor cluster and in my notary server and signer pods I’m getting the following output

2021/10/05 16:55:06 Updating database.
2021/10/05 16:55:06 schema_migrations table does not require update, skip.
no change
notarysigner database migrated to latest version
{"level":"info","msg":"Version: 0.6.1, Git commit: d6e1431f","time":"2021-10-05T16:55:06Z"}
{"level":"fatal","msg":"failed to create a new keydbstore: pq: unknown authentication response: 10","time":"2021-10-05T16:55:06Z"}

I believe this has to do with the scram-sha-256 client library needing to be updated as per this post on stackoverflow.

Is this something I can work around or does this need to be fixed in the codebase? Thank you!

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 4
Comments: 15 (1 by maintainers)

Most upvoted comments

@InderpreetSaini Here you go! He links to the code you can use in his response to me.

kevinlmadison on Dec 17, 2021

I was having the same issue, but the link mentioned above worked for me in resolving it. Are there any plans on adding support for SCRAM-SHA-256?

djtaylor on Feb 1, 2022

@InderpreetSaini @kevinlmadison

HI , i am facing same issue , with harbor using postgres operator I am using the postgres cluster https://access.crunchydata.com/documentation/postgres-operator/5.0.4/quickstart/

i tried patching secret with SCRAM-SHA-256 as mentioned above its not solving 😦 could you pls guide me

oc logs harbor-notary-signer-5d5bf66dbb-p9kzb 2022/04/13 20:25:12 Updating database. 2022/04/13 20:25:12 schema_migrations table does not require update, skip. no change notarysigner database migrated to latest version {“level”:“info”,“msg”:“Version: 0.6.1, Git commit: d6e1431f”,“time”:“2022-04-13T20:25:12Z”} {“level”:“fatal”,“msg”:“failed to create a new keydbstore: pq: unknown authentication response: 10”,“time”:“2022-04-13T20:25:12Z”}

harbor values.yaml : external: host: “hippo-primary.postgres-operator.svc” port: “5432” username: hippo password: datalake coreDatabase: “registry” notaryServerDatabase: “notaryserver” notarySignerDatabase: “notarysigner” sslmode: “require”

Hi @Ramki33 , as per my understanding, notary in Harbor does not support SCRAM-SHA-256 encrypted password authentication. Have you tried generating the verifier using algorithm value as md5 instead of scram-sha-256?

Besides the latest version of Harbor 2.5.0 supports Cosign integration as an image signing solution along with Notary. So you have the option to go along with Cosign, instead of Notary.

InderpreetSaini on Apr 16, 2022