
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>RXRW</title>
      <link>https://stb.id.au/blog</link>
      <description>Building applications, securing infrastructure and applications, and everything in-between.</description>
      <language>en-us</language>
      <managingEditor>dev@stb.id.au (Shane Boulden)</managingEditor>
      <webMaster>dev@stb.id.au (Shane Boulden)</webMaster>
      <lastBuildDate>Tue, 05 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://stb.id.au/tags/spn/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://stb.id.au/blog/openshift-entra-spn</guid>
    <title>Microsoft Entra SPN auth with OpenShift</title>
    <link>https://stb.id.au/blog/openshift-entra-spn</link>
    <description>OpenShift 4.20 introduced support for direct OpenID Connect authentication, allowing you to configure the OpenShift API / console to authenticate directly with OpenID Connect providers. In this article I take a closer look at one of the use cases this enables - Microsoft Entra Service Principal Name (SPN) direct authentication to OpenShift.</description>
    <pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate>
    <author>dev@stb.id.au (Shane Boulden)</author>
    <category>openshift</category><category>entra</category><category>authentication</category><category>authorisation</category><category>spn</category><category>service</category><category>principal</category>
  </item>

    </channel>
  </rss>
