
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Fri, 12 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/logout/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/devops/2026-06-12-single-logout-session-termination-design.en</guid>
    <title>The Hard Problem of Single Logout (SLO) — Designing Front-Channel and Back-Channel Logout</title>
    <link>https://www.youngju.dev/blog/devops/2026-06-12-single-logout-session-termination-design.en</link>
    <description>In SSO, logout is harder than login. This post covers the three-layer session model, how OIDC RP-Initiated/Front-Channel/Back-Channel Logout work and where they fail, the logout token JWT structure, the realistic failure rates of SAML SLO, Keycloak configuration, and how 2026 browser third-party cookie blocking reshapes logout design.</description>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>sso</category><category>oidc</category><category>saml</category><category>keycloak</category><category>logout</category><category>security</category><category>session</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/devops/2026-06-12-single-logout-session-termination-design.ja</guid>
    <title>Single Logout(SLO)の難しさ — Front-Channel、Back-Channelログアウトの設計</title>
    <link>https://www.youngju.dev/blog/devops/2026-06-12-single-logout-session-termination-design.ja</link>
    <description>SSOにおいてログアウトはログインより難しい問題です。セッション3層モデル、OIDC RP-Initiated/Front-Channel/Back-Channel Logoutの動作と限界、logout token JWTの構造、SAML SLOの現実的な失敗率、Keycloakの設定、そして2026年のブラウザのサードパーティCookieブロックがログアウト設計に与える影響まで整理します。</description>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>sso</category><category>oidc</category><category>saml</category><category>keycloak</category><category>logout</category><category>security</category><category>session</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/devops/2026-06-12-single-logout-session-termination-design</guid>
    <title>Single Logout(SLO)의 어려움 — Front-Channel, Back-Channel 로그아웃 설계</title>
    <link>https://www.youngju.dev/blog/devops/2026-06-12-single-logout-session-termination-design</link>
    <description>SSO에서 로그아웃은 로그인보다 어렵습니다. 세션 3계층 모델, OIDC RP-Initiated/Front-Channel/Back-Channel Logout의 동작과 한계, logout token JWT 구조, SAML SLO의 현실적 실패율, Keycloak 설정, 그리고 2026년 브라우저 서드파티 쿠키 차단이 로그아웃 설계에 미치는 영향까지 정리합니다.</description>
    <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>sso</category><category>oidc</category><category>saml</category><category>keycloak</category><category>logout</category><category>security</category><category>session</category>
  </item>

    </channel>
  </rss>
