#smallrye-jwt

Change in Quarkus SmallRye JWT expiration tolerance leads to downstream expiry state inconsistency

Goal: When a JWT is accepted under the configured expiration tolerance, the application should treat the token as non‑expired for all internal purposes, including downstream propagation to identity providers or audit systems, so that services relying on the token’s expiry state see a consistent view. Constraint: In Quarkus 3.2 and later the property quarkus.