<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Entra on mishraJi</title>
    <link>https://blog.mishraji.org/tags/entra/</link>
    <description>Recent content in Entra on mishraJi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.mishraji.org/tags/entra/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Certificate vs Client Secret in the Client Credentials Flow</title>
      <link>https://blog.mishraji.org/posts/client-secret-vs-certificate-based-authentication/</link>
      <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mishraji.org/posts/client-secret-vs-certificate-based-authentication/</guid>
      <description>&lt;h1 id=&#34;certificate-vs-client-secret-in-the-client-credentials-flow&#34;&gt;Certificate vs Client Secret in the Client Credentials Flow&lt;/h1&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Most OAuth flows are about a &lt;em&gt;user&lt;/em&gt; proving who they are. The &lt;strong&gt;client credentials flow&lt;/strong&gt; is the odd one out — there is no user. It is machine-to-machine. A backend service, a daemon, a scheduled job — something with no human sitting in front of it — needs to call an API and prove &lt;em&gt;it&lt;/em&gt; is who it claims to be.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
