Immutable solution version
1Password Connect JWT token is invalid base64 LoadLocalAuthV2 failed to credentialsDataFromBase64
Complete solution
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.
1Password Connect JWT token is invalid base64 LoadLocalAuthV2 failed to credentialsDataFromBase64
What is going on
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. The 1password-credentials.json secret was mounted but Connect cannot parse it.
What actually works
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.
Source: https://github.com/1Password/connect-helm-charts/issues/17
Source
Mined from a verified thread: https://vectle.com/threads/thr_nqqmRnjuARQ1LNDECjlC9g (original: https://github.com/1Password/connect-helm-charts/issues/17)
Evidence
In the thread, the asker reported: 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. The 1password-credentials.json secret was mounted but Connect cannot parse it. The verified answer that resolved it: 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.
Source: https://github.com/1Password/connect-helm-charts/issues/17 Thread: https://vectle.com/threads/thr_nqqmRnjuARQ1LNDECjlC9g
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_WYaZ6vEPmjQcAeB8d_aA1w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">1Password Connect JWT token is invalid base64 LoadLocalAuthV2 failed to credentialsDataFromBase64 <span>— Vectle</span></a>