<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operations on temporal-operator</title><link>https://temporal-operator.bmorton.dev/operations/</link><description>Recent content in Operations on temporal-operator</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://temporal-operator.bmorton.dev/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>Authentication &amp; Authorization</title><link>https://temporal-operator.bmorton.dev/operations/authentication/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://temporal-operator.bmorton.dev/operations/authentication/</guid><description>&lt;h1 id="authentication--authorization">
 Authentication &amp;amp; Authorization
 &lt;a class="anchor" href="#authentication--authorization">#&lt;/a>
&lt;/h1>
&lt;p>This guide covers configuring Microsoft Entra (Azure AD) authentication and
authorization for temporal-operator — both &lt;strong>server-side JWT validation&lt;/strong> for
programmatic callers and &lt;strong>UI OIDC login&lt;/strong> for human users.&lt;/p>
&lt;h2 id="concepts">
 Concepts
 &lt;a class="anchor" href="#concepts">#&lt;/a>
&lt;/h2>
&lt;h3 id="authentication-vs-authorization">
 Authentication vs. authorization
 &lt;a class="anchor" href="#authentication-vs-authorization">#&lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Authentication&lt;/strong> — verifying that an incoming JWT was issued by a trusted
identity provider (Microsoft Entra) and has a valid signature. Temporal
performs this by fetching public keys from a JWKS endpoint and validating
the token&amp;rsquo;s signature, issuer, and audience.&lt;/li>
&lt;li>&lt;strong>Authorization&lt;/strong> — deciding whether an authenticated caller may perform a
specific operation on a specific Temporal namespace. Temporal&amp;rsquo;s built-in
&lt;code>default&lt;/code> authorizer reads a permissions claim from the JWT and maps it to
per-namespace roles.&lt;/li>
&lt;/ul>
&lt;h3 id="jwks--jwt-key-provider">
 JWKS / JWT key provider
 &lt;a class="anchor" href="#jwks--jwt-key-provider">#&lt;/a>
&lt;/h3>
&lt;p>Temporal&amp;rsquo;s frontend service fetches public keys from one or more JWKS
(&lt;code>keySourceURIs&lt;/code>) to validate incoming token signatures. The operator
configures this through &lt;code>spec.authorization.jwtKeyProvider&lt;/code>. When you set
&lt;code>spec.authorization.entra.tenantID&lt;/code>, the operator automatically derives the
correct JWKS URL:&lt;/p></description></item></channel></rss>