Our community is getting an upgrade on July 2nd! Learn more in the FAQs →
Forum Discussion
Anonymous
4 years agoinvalid token for credentials file 500: Internal Server Error
Hi I configured my secret with base64 file as mentioned in the article here:
https://github.com/1password/onepassword-operator
The connect-sync is working well as in the log below:
{"log_mess...
Anonymous
4 years agoHi there,
It looks like there is an issue with your credentials file. Can you validate that the credentials data stored in the op-credentials secret is what we would expect. That is, if we run kc get secret op-credentials -o json, the data field for 1password-credentials.json returns the string from your credentials file encoded twice (once automatically by Kubernetes secrets, and once by encoding them in the encoding step in the operator documentation.)
If you are having issues base64 encoding the credentials file, you can also try deploying the operator and connect using our https://github.com/1Password/connect-helm-charts/tree/main/charts/connect, as the helm chart will handle this for you.