DongHyeonkaandClaude Opus 5
e856e7af4d
One user session carries a client session per application, so visiting the second app skips the login screen. Deleting the identity provider session leaves both application sessions untouched and both apps keep serving, because the identity provider, the application session and the access token each have their own lifetime. That inverts the B-2 finding: there the app session was cleared and the surviving SSO session let the user straight back in. Either way, clearing one side leaves the other. It also means an identity provider outage is a single point of failure for logging in, not for already-authenticated users, and the failure arrives late and all at once. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
7 lines
563 B
YAML
7 lines
563 B
YAML
- main [ref=f46e2]:
|
|
- heading "AP3 · Backend-for-Frontend" [level=1] [ref=f46e3]
|
|
- paragraph [ref=f46e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
|
|
- button "Keycloak 로그인" [ref=f46e5] [cursor=pointer]
|
|
- button "token 경계 확인" [ref=f46e6] [cursor=pointer]
|
|
- button "BFF 경유 API 호출" [ref=f46e7] [cursor=pointer]
|
|
- button "CSRF token으로 상태 변경" [ref=f46e8] [cursor=pointer] |