DongHyeonkaandClaude Opus 5
aa2c3907f5
Adding a higher-priority RSA provider leaves both kids in JWKS, so tokens signed before and after the rotation both validate. Deleting the old provider makes its tokens 401 immediately, and the resource server's JWKS cache does not buy a grace period because an unknown kid triggers a refetch. The encryption key Q3 asks about does not exist yet, since B-2 showed the tokens are stored as plaintext JWTs, so the measured signing-key rotation is what its design has to copy: write with one key, read with several, and keep the overlap longer than the lifetime of anything signed with the old one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
10 lines
376 B
Plaintext
10 lines
376 B
Plaintext
=== [1] 회전 전: 토큰 발급 + JWKS 상태 ===
|
|
발급 토큰의 kid: OY-caYDNGoP4HMAz-Q9UPTU-DM1i896NuzUZu6gfCqM
|
|
JWKS 의 RS256 키 수: 1
|
|
JWKS kid 목록:
|
|
{"keys":[{"kid":"gokjn0zFUok8r7JVqW1cxuyojH1bTT87vzfQG9RrFX4"
|
|
{"kid":"OY-caYDNGoP4HMAz-Q9UPTU-DM1i896NuzUZu6gfCqM"
|
|
|
|
=== [2] 그 토큰이 지금 통하는가 (리소스 서버) ===
|
|
/api/me HTTP 200
|