fix(official-bots): mount JWT public key from ncs-jwt-keys #414

Merged
Janis merged 2 commits from fix/official-bots-jwt-mount into main 2026-06-17 09:51:17 +02:00

2 Commits

Author SHA1 Message Date
Janis f0dc9fd145 chore(official-bots): debug logging for JWT verify on staging
Delete PR Branch On Close / delete-branch (pull_request) Successful in 6s
Enable DEBUG for io.smallrye.jwt and io.quarkus.security on the
official-bots rollout in staging only (container env, not the shared
ConfigMap) to diagnose the persistent 401. Remove after root cause.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 09:50:04 +02:00
Janis cfb25eff8c fix(official-bots): mount JWT public key from ncs-jwt-keys
Delete PR Branch On Close / delete-branch (pull_request) Successful in 6s
The official-bots rollout never mounted the ncs-jwt-keys secret nor set
JWT_PUBLIC_KEY_PATH, so the service fell back to the image-baked
public.pem, which does not match the deployed signing key. Every token
failed RS256 verification -> 401.

Mount ncs-jwt-keys at /secrets/jwt and point JWT_PUBLIC_KEY_PATH there,
mirroring account/core/tournament. Verify-only, no private key.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 09:42:21 +02:00