NetworkPolicy allows gateway→iam only on ports 9000/9443.
Gateway config was using port 80, causing JWT validation failures.
Changes made:
auth.jwksUrl: port 80 → 9000
auth.tokenUrl: port 80 → 9000
iam.upstream: port 80 → 9000
This fixes JWKS refresh and JWT token validation.
Fix gateway authentik port from 80 to 9000
NetworkPolicy allows gateway→iam only on ports 9000/9443.
Gateway config was using port 80, causing JWT validation failures.
Changes made:
- auth.jwksUrl: port 80 → 9000
- auth.tokenUrl: port 80 → 9000
- iam.upstream: port 80 → 9000
This fixes JWKS refresh and JWT token validation.
NetworkPolicy allows gateway→iam only on ports 9000/9443, but config
used port 80 for JWKS fetch and token endpoints. This caused
'operation not permitted' errors and JWKS refresh failures.
Affects:
- auth.jwksUrl: uses port 9000 (Authentik HTTP)
- auth.tokenUrl: uses port 9000 for token exchange
- iam adapter upstream: routes to port 9000
Fixes: Gateway unable to validate JWT tokens, all chat/inference requests
returned 401 with 'token is unverifiable' error.
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.
Fix gateway authentik port from 80 to 9000
NetworkPolicy allows gateway→iam only on ports 9000/9443.
Gateway config was using port 80, causing JWT validation failures.
Changes made:
This fixes JWKS refresh and JWT token validation.
3188ce3e6ato2d558304122d55830412to45254a48b0