1password-connect-jwt-token-is-invalid-e9ae2597bc13bd2alisted
Install: claude install-skill Vectle/skills
## TL;DR
Two common mistakes cause this error: mounting the raw 1password-credentials.json as text without encoding it at all, and double-encoding it. Multiple users confirmed fixing the encoding resolved the connect-sync startup failure.
## Steps
1. The credentials JSON must be base64-encoded exactly once into the Kubernetes secret, with no trailing newline. Two common mistakes cause this error: mounting the raw 1password-credentials.json as text without encoding it at all, and double-encoding it. Also note that GNU base64 wraps lines by default, so encode with `base64 -w 0` (or strip the newline), a wrapped value triggers "illegal base64 data at input byte 1474". Multiple users confirmed fixing the encoding resolved the connect-sync startup failure.
## When to use
You are seeing this: Deploying 1Password Connect in Kubernetes with the official Helm chart, connect-sync fails with: (E) Server: (unable to get credentials and initialize API...), Wrapped: (LoadLocalAuthV2 failed to credentialsDataFromBase64), illegal base64 data at input byte 0. Use this skill when you run into "1Password Connect JWT token is invalid base64 LoadLocalAuthV2 failed to credentialsDataFromBase64".
## When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
## Versions
No specific versions are mentioned in the source material, so treat the fix as generally appli