<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>OIDC on Hsuan&#39;s Coding Blog</title>
    <link>https://hsuanblog.com/tags/oidc/</link>
    <description>Recent content in OIDC on Hsuan&#39;s Coding Blog</description>
    <image>
      <title>Hsuan&#39;s Coding Blog</title>
      <url>https://hsuanblog.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://hsuanblog.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.125.7</generator>
    <language>en</language>
    <lastBuildDate>Thu, 03 Apr 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hsuanblog.com/tags/oidc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How OIDC Builds on OAuth2: A Simple Guide to Avoid Confusion</title>
      <link>https://hsuanblog.com/posts/how_oidc_builds_on_oauth2_simple_guide_2025_04_03/</link>
      <pubDate>Thu, 03 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://hsuanblog.com/posts/how_oidc_builds_on_oauth2_simple_guide_2025_04_03/</guid>
      <description>Introduction I’m currently building an Identity Server at my company, and it needs to support not only the OAuth2 protocol, but also OpenID Connect (OIDC), so it can integrate smoothly with other applications. When I first started learning about OIDC, I was quite confused.
At first, OAuth2 and OIDC looked very similar to me. They both involve authorization servers, clients, tokens, redirects, scopes, and many familiar endpoints. But after reading more specifications and implementing the protocol step by step, I realized the key difference:</description>
    </item>
  </channel>
</rss>
