<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oauth2 on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/oauth2/</link>
    <description>Recent content in Oauth2 on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/oauth2/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Mock OAuth2 Servers: navikt vs MockServer vs Keycloak</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-mock-oauth2-servers-navikt-mockserver-keycloak-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-mock-oauth2-servers-navikt-mockserver-keycloak-guide/</guid>
      <description>&lt;p&gt;Mock OAuth2 servers are essential for testing authentication flows without depending on real identity providers like Google, Okta, or Auth0. They let you simulate token issuance, redirect flows, and error conditions locally — critical for CI/CD pipelines, integration testing, and development environments. This guide compares three self-hosted mock OAuth2 solutions with Docker deployment configs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
