DongHyeonkaandClaude Opus 5
e62bbb4df0
The authorized client repository is AuthenticatedPrincipalOAuth2AuthorizedClientRepository, keyed by principal with no session id in it, which is the mechanism behind the sharing problem Q1 and Q3 describe. Sharing a store does not fix a lookup key. Five problems on the way in: only build output was committed under bff/, a duplicate YAML key broke the image build and was invisible until the full log was captured, env placeholders without defaults broke the tests, actuator was behind the login redirect so a 200 was the login page, and the 117KB beans response failed through the proxy. Deploying two replicas made the login itself fail before any experiment started, because the authorization request lives in per-instance memory and the callback lands elsewhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
7 lines
563 B
YAML
7 lines
563 B
YAML
- main [ref=f24e2]:
|
|
- heading "AP3 · Backend-for-Frontend" [level=1] [ref=f24e3]
|
|
- paragraph [ref=f24e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
|
|
- button "Keycloak 로그인" [ref=f24e5] [cursor=pointer]
|
|
- button "token 경계 확인" [ref=f24e6] [cursor=pointer]
|
|
- button "BFF 경유 API 호출" [ref=f24e7] [cursor=pointer]
|
|
- button "CSRF token으로 상태 변경" [ref=f24e8] [cursor=pointer] |