The paperless-oidc Secret stores the OIDC client secret twice: as client-secret and inside SOCIALACCOUNT_PROVIDERS_JSON (which is what allauth reads). Only the JSON copy was updated during the ZITADEL migration, so client-secret held a superseded rotation.
Invisible in normal use, but misleading when verifying: a token-endpoint probe using client-secret returns invalid secret while Paperless logs in correctly. Both keys now carry the same live value.
Verified: the re-encrypted SOPS file decrypts and both keys compare equal.
The `paperless-oidc` Secret stores the OIDC client secret twice: as `client-secret` and inside `SOCIALACCOUNT_PROVIDERS_JSON` (which is what allauth reads). Only the JSON copy was updated during the ZITADEL migration, so `client-secret` held a superseded rotation.
Invisible in normal use, but misleading when verifying: a token-endpoint probe using `client-secret` returns `invalid secret` while Paperless logs in correctly. Both keys now carry the same live value.
Verified: the re-encrypted SOPS file decrypts and both keys compare equal.
The paperless-oidc Secret carries the OIDC client secret twice: once as
`client-secret` and once inside SOCIALACCOUNT_PROVIDERS_JSON, which is what
allauth actually reads. Only the JSON copy was updated during the ZITADEL
migration, so `client-secret` held a superseded rotation.
That is invisible in normal use but makes the Secret misleading to verify:
a token-endpoint probe using `client-secret` answers "invalid secret" while
Paperless itself logs in fine. Both keys now carry the same live value.
rock
merged commit 894d746b0d into main2026-10-31 21:10:28 +00:00
rock
deleted branch fix/paperless-oidc-secret-align2026-10-31 21:10:52 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
paperless-oidcSecret stores the OIDC client secret twice: asclient-secretand insideSOCIALACCOUNT_PROVIDERS_JSON(which is what allauth reads). Only the JSON copy was updated during the ZITADEL migration, soclient-secretheld a superseded rotation.Invisible in normal use, but misleading when verifying: a token-endpoint probe using
client-secretreturnsinvalid secretwhile Paperless logs in correctly. Both keys now carry the same live value.Verified: the re-encrypted SOPS file decrypts and both keys compare equal.