<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chuck</title>
    <description>The latest articles on DEV Community by Chuck (@chuck1in).</description>
    <link>https://dev.to/chuck1in</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F942363%2Fac807fd4-f5b0-40ac-9950-cb474d3670a1.png</url>
      <title>DEV Community: Chuck</title>
      <link>https://dev.to/chuck1in</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chuck1in"/>
    <language>en</language>
    <item>
      <title>An OIDC authentication library that supports self hosting and has complete test cases</title>
      <dc:creator>Chuck</dc:creator>
      <pubDate>Fri, 26 Apr 2024 09:10:38 +0000</pubDate>
      <link>https://dev.to/chuck1in/an-oidc-authentication-library-that-supports-self-hosting-and-has-complete-test-cases-40nc</link>
      <guid>https://dev.to/chuck1in/an-oidc-authentication-library-that-supports-self-hosting-and-has-complete-test-cases-40nc</guid>
      <description>&lt;p&gt;&lt;a href="https://github.com/chuck1in/nw-auth"&gt;https://github.com/chuck1in/nw-auth&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Made an identity authentication library based on the OIDC process, which supports third-party platforms such as GitHub, WeChat, Google, Twitter, Feishu, and Sina. In theory, it also supports self-deployed OIDC authentication servers. Since it has not been advertised, I don't know if any users are using it.&lt;/p&gt;

&lt;p&gt;🎉 The features of this library are as follows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🍒 Small code size&lt;/li&gt;
&lt;li&gt;🍋 Few exposed interfaces&lt;/li&gt;
&lt;li&gt;🥝 No runtime dependencies&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Recently, I used my spare time to add a self-test page to this library, which is convenient for everyone to confirm whether the three-party login function of the library can operate normally through the visual interface.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fs9sokk3co3yq5gx5fbyz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fs9sokk3co3yq5gx5fbyz.png" alt="seflhost-test" width="800" height="387"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This page is made with sveltekit. I don't specialize in front-end. I didn't think there was much work, but it ended up taking a lot of time and effort. &lt;/p&gt;

&lt;p&gt;If you find this library useful, I hope you can give me some ⭐ for encouragement. Thank you for your support.&lt;/p&gt;

&lt;p&gt;If you are willing to contribute code to this library, you can simply add more third-party login platforms based on the existing structure. 👏 👏 👏&lt;/p&gt;

</description>
      <category>node</category>
      <category>typescript</category>
      <category>svelte</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
