Closed acollign closed 1 year ago
Hi - I just tested using you example and it work fine for me.
Make sure you delete any old PVCs that might contain a previous password Check kubernetes events for any issues mounting the secret to the database pod
Hi @ojhughes,
I just tested using you example and it work fine for me. Make sure you delete any old PVCs that might contain a previous password
Thanks for testing this case. I can reproduce the bug with a clean kubernetes install, without any PVC.
May ask I you which version you are testing? I tested with neo4j-5.7.0.
yes 5.7 on GKE
I just reproduced the same issue on another fresh install. I don´t have any errors in the events. Everything looks good except that I cannot log in.
Is there any debugging steps I could follow to identify the root cause ? Thanks in advance for your help.
Not really, it works on GKE / AKS / EKS and we can't test against every type of cluster.
can you log in using Neo4j Browser out of interest?
I found out the issue comes from a silly mistake when encoding the password in base64. The base64 encoded password value in the test file ends with a \n
. The correct base64 encoded value of longpassword
is bmVvNGovbG9uZ3Bhc3N3b3Jk
which is what neo4j rightfully expect.
Thank you for helping out.
Contact Details
No response
What happened?
Using the chart version 5.7.0, I am unable to log in a neo4j community standalone installation when defining the initial password via a secret.
To reproduce:
longpassword
.NEO4J_AUTH
is set to base64 value ofneo4j/longpassword
neo4j.passwordFromSecret
toneo4j-password
in values.yamlvolumes: data: mode: "dynamic" dynamic: storageClassName: openebs-hostpath
... $ kubectl run --rm -it --image "neo4j:5.7.0" cypher-shell \ -- cypher-shell -a "neo4j://my-neo4j-release.default.svc.cluster.local:7687" -u neo4j -p "$(kubectl get secret neo4j-password -o go-template='{{.data.NEO4J_AUTH | base64decode }}' | cut -d '/' -f2)" ...