<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Avild Blog]]></title><description><![CDATA[Avild Blog]]></description><link>https://blog.avild.com</link><image><url>https://substackcdn.com/image/fetch/$s_!VfYB!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F486aa0c5-66ac-40cf-89ae-08236594768c_1280x1280.png</url><title>Avild Blog</title><link>https://blog.avild.com</link></image><generator>Substack</generator><lastBuildDate>Sun, 22 Nov 2026 01:56:45 GMT</lastBuildDate><atom:link href="https://blog.avild.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Ali Mammadzadeh]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[avild@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[avild@substack.com]]></itunes:email><itunes:name><![CDATA[Ali Mammadzadeh]]></itunes:name></itunes:owner><itunes:author><![CDATA[Ali Mammadzadeh]]></itunes:author><googleplay:owner><![CDATA[avild@substack.com]]></googleplay:owner><googleplay:email><![CDATA[avild@substack.com]]></googleplay:email><googleplay:author><![CDATA[Ali Mammadzadeh]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[From Passwords to Agents: A Practical Tour of Modern Identity]]></title><description><![CDATA[A lot of modern breaches don&#8217;t start with someone breaking in.]]></description><link>https://blog.avild.com/p/from-passwords-to-agents-a-practical</link><guid isPermaLink="false">https://blog.avild.com/p/from-passwords-to-agents-a-practical</guid><dc:creator><![CDATA[Elshad Ghaybaliyev]]></dc:creator><pubDate>Thu, 19 Nov 2026 13:16:05 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!PTlG!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A lot of modern breaches don&#8217;t start with someone breaking in. They start with someone logging in, using a password that was phished, reused, or leaked.</p><p>Applications have moved to the cloud and people work from anywhere, so the office firewall no longer marks where &#8220;inside&#8221; ends. What decides access now is identity: who you are, how you proved it, and what you&#8217;re allowed to touch. That is why security teams call identity the new perimeter.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.avild.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Avild Blog! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>I&#8217;m an IAM intern, and I&#8217;ve spent my internship taking <a href="https://www.keycloak.org/">Keycloak</a>, an open-source identity platform, apart. I set up realms and clients, traced logins step by step, and studied how CERN runs it as the single sign-on for <a href="https://indico.cern.ch/event/1678348/contributions/7063020/attachments/3314358/5932219/The%20Many%20Faces%20of%20Authentication%20and%20Authorisation%20at%20CERN.pdf">roughly 14,000 services</a>. This post is the map I wish I&#8217;d had on day one.</p><p>In about ten minutes you&#8217;ll learn:</p><ul><li><p>the handful of concepts every identity system shares</p></li><li><p>how we got from LDAP and Kerberos to OAuth and OpenID Connect</p></li><li><p>why passkeys are replacing passwords</p></li><li><p>who the main identity providers are and how they differ</p></li><li><p>the newest problem in the field: giving AI agents an identity of their own</p></li></ul><h2><strong>The core concepts, in plain terms</strong></h2><p>Identity systems answer four questions:</p><ul><li><p><strong>Identification</strong>: who do you claim to be? A username or an email.</p></li><li><p><strong>Authentication (AuthN)</strong>: can you prove it? A password, a passkey, a fingerprint.</p></li><li><p><strong>Authorization (AuthZ)</strong>: what are you allowed to do? Read this file, approve that payment.</p></li><li><p><strong>Accounting</strong>: what did you actually do? Logs and audit trails.</p></li></ul><p>Mixing up authentication and authorization is the most common beginner mistake. As we&#8217;ll see, that confusion is baked into the history of OAuth.</p><p>Two roles show up in every login flow. The <strong>Identity Provider (IdP)</strong> holds the accounts and verifies users. The <strong>Service Provider (SP)</strong>, called a <strong>Relying Party (RP)</strong> in OpenID Connect, is the app that trusts the IdP&#8217;s answer instead of checking passwords itself.</p><p>That trust makes <strong>Single Sign-On (SSO)</strong> possible: log in once at the IdP, and every connected app accepts it. <strong>Federation</strong> stretches the same idea across organizations, so your company&#8217;s IdP can vouch for you inside a vendor&#8217;s product.</p><p>Accounts also have a lifecycle. <strong>Provisioning</strong> creates them when someone joins, and <strong>deprovisioning</strong> removes them when someone leaves. Forgotten accounts are a classic way in for attackers, so most organizations automate this with <a href="https://datatracker.ietf.org/doc/html/rfc7644">SCIM</a>, a standard API for syncing users and groups between systems.</p><p>Finally, access models decide who gets what:</p><ul><li><p><strong>RBAC</strong> (role-based): permissions attach to roles such as &#8220;editor&#8221; or &#8220;billing admin.&#8221;</p></li><li><p><strong>ABAC</strong> (attribute-based): rules look at attributes such as department, device, or time of day.</p></li><li><p><strong>Least privilege</strong>: whichever model you pick, grant only what the job needs.</p></li></ul><h2><strong>How we got here: a short history of identity protocols</strong></h2><p>Every protocol on this list exists because the one before it hit a wall.</p><p><strong>Local accounts.</strong> At first, each system kept its own usernames and passwords. Ten systems meant ten passwords, and ten places to forget to delete an account.</p><p><strong>Directories and tickets (1990s).</strong> <a href="https://datatracker.ietf.org/doc/html/rfc4511">LDAP</a> gave an organization one central directory of users. <a href="https://datatracker.ietf.org/doc/html/rfc4120">Kerberos</a> added tickets, so a user could prove who they were once and then reach many services. <a href="https://datatracker.ietf.org/doc/html/rfc2865">RADIUS</a> did a similar job for network access such as VPN and Wi-Fi. All three assume you are inside a trusted corporate network. They still run underneath many enterprises today, most visibly in Active Directory.</p><p><strong>Federation for the web (2005).</strong> Then applications moved into the browser and onto other companies&#8217; servers. <a href="https://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf">SAML 2.0</a> let an IdP hand a signed XML document, called an assertion, to an outside application through the browser. It was the first widely adopted answer to cross-company SSO, which is why so much enterprise software still speaks it. Three things made it stick. It needed nothing but a browser, so the two companies required no direct network link. It merged earlier competing efforts (SAML 1.1, Liberty Alliance ID-FF, and Shibboleth) into one standard. And a single assertion could carry the user&#8217;s attributes and roles along with the login.</p><p><strong>The API era (2012).</strong> Mobile apps and APIs needed something lighter, plus a way to give an app limited access without handing over a password. <a href="https://datatracker.ietf.org/doc/html/rfc6749">OAuth 2.0</a> solved that with access tokens. Note what it is for: OAuth is about <em>authorization</em>. It tells an API what an app may do, not who the user is.</p><p><strong>An identity layer (2014).</strong> Developers used OAuth for login anyway, each in a slightly different way. <a href="https://openid.net/specs/openid-connect-core-1_0.html">OpenID Connect (OIDC)</a> standardized it by adding an ID token on top of OAuth 2.0.</p><p><strong>Hardening (2015 to today).</strong> <a href="https://datatracker.ietf.org/doc/html/rfc7636">PKCE</a> closed a hole that let attackers intercept authorization codes. A decade of similar lessons is collected in the <a href="https://datatracker.ietf.org/doc/html/rfc9700">OAuth 2.0 Security Best Current Practice</a> and is being folded into <a href="https://datatracker.ietf.org/doc/draft-ietf-oauth-v2-1/">OAuth 2.1</a>, which is still an IETF draft. OAuth 2.1 is not a new protocol. It makes PKCE mandatory and removes the risky implicit and password grants.</p><p>For tokens, the same best practices come down to four habits:</p><ul><li><p><strong>One audience, smallest scope.</strong> An access token should work at a single API and carry only the permissions the task needs.</p></li><li><p><strong>Bound to the client.</strong> Tie the token to the app that received it, using DPoP or mutual TLS, so a stolen copy is useless.</p></li><li><p><strong>Rotating refresh tokens.</strong> Apps that cannot keep a secret, such as mobile and single-page apps, get a new refresh token on every use, unless the token is bound to the client.</p></li><li><p><strong>No tokens in URLs.</strong> URLs leak through browser history, logs, and referrer headers.</p></li></ul><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!PTlG!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!PTlG!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 424w, https://substackcdn.com/image/fetch/$s_!PTlG!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 848w, https://substackcdn.com/image/fetch/$s_!PTlG!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 1272w, https://substackcdn.com/image/fetch/$s_!PTlG!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!PTlG!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png" width="576" height="659" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/80177330-585d-4e81-80f2-66333eb046f0_576x659.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:659,&quot;width&quot;:576,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Timeline of identity protocols from LDAP and Kerberos in 1993 to OAuth 2.1, grouped into four eras&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Timeline of identity protocols from LDAP and Kerberos in 1993 to OAuth 2.1, grouped into four eras" title="Timeline of identity protocols from LDAP and Kerberos in 1993 to OAuth 2.1, grouped into four eras" srcset="https://substackcdn.com/image/fetch/$s_!PTlG!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 424w, https://substackcdn.com/image/fetch/$s_!PTlG!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 848w, https://substackcdn.com/image/fetch/$s_!PTlG!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 1272w, https://substackcdn.com/image/fetch/$s_!PTlG!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F80177330-585d-4e81-80f2-66333eb046f0_576x659.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><em>Three decades of identity protocols, from directories inside the network to tokens on the open web.</em></p><h2><strong>The protocols you&#8217;ll actually meet</strong></h2><p>In day-to-day work, three names cover almost everything: SAML, OAuth 2.0, and OpenID Connect.</p><h3><strong>SAML or OIDC?</strong></h3><p>Both solve login and SSO, so the application usually decides for you:</p><ul><li><p><strong>A new web, mobile, or single-page app:</strong> use OIDC. It is JSON-based and works naturally with APIs.</p></li><li><p><strong>An older enterprise system or a SaaS product that only speaks SAML:</strong> use SAML.</p></li></ul><p>A good IdP handles both at once. In Keycloak, one realm can serve a new portal over OIDC and an old HR system over SAML, and the user still logs in only once.</p><h3><strong>OAuth 2.0 grant types</strong></h3><p>A grant type is simply the way an app obtains a token. Three are worth knowing:</p><ul><li><p><strong>Authorization code with PKCE:</strong> a person logs in through the browser. This is the default for web, mobile, and single-page apps.</p></li><li><p><strong>Client credentials:</strong> no person is involved. One service calls another using its own identity.</p></li><li><p><strong>Device flow</strong> (<a href="https://datatracker.ietf.org/doc/html/rfc8628">RFC 8628</a>): for smart TVs and command-line tools. You approve the login on your phone.</p></li></ul><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!HF4Q!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!HF4Q!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 424w, https://substackcdn.com/image/fetch/$s_!HF4Q!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 848w, https://substackcdn.com/image/fetch/$s_!HF4Q!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 1272w, https://substackcdn.com/image/fetch/$s_!HF4Q!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!HF4Q!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png" width="576" height="629" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:629,&quot;width&quot;:576,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Sequence diagram of an OpenID Connect login using the authorization code flow with PKCE&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Sequence diagram of an OpenID Connect login using the authorization code flow with PKCE" title="Sequence diagram of an OpenID Connect login using the authorization code flow with PKCE" srcset="https://substackcdn.com/image/fetch/$s_!HF4Q!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 424w, https://substackcdn.com/image/fetch/$s_!HF4Q!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 848w, https://substackcdn.com/image/fetch/$s_!HF4Q!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 1272w, https://substackcdn.com/image/fetch/$s_!HF4Q!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9bb625bf-c65d-4a2f-85ab-03e2a7f80aad_576x629.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><em>An OIDC login with the authorization code flow and PKCE. Tokens travel only over the direct server-to-server call, never through the browser.</em></p><h3><strong>Three tokens, one hotel</strong></h3><p>Think of the IdP as a hotel reception desk:</p><ul><li><p><strong>ID token:</strong> your passport. It tells the app who you are, and it is never sent to an API.</p></li><li><p><strong>Access token:</strong> your room key card. The app presents it to the API on every request. It is short-lived on purpose: Keycloak&#8217;s default is five minutes.</p></li><li><p><strong>Refresh token:</strong> lets the app get a new key card without sending you back to reception.</p></li></ul><p>Most of these are <strong>JWTs</strong> (<a href="https://datatracker.ietf.org/doc/html/rfc7519">RFC 7519</a>): three Base64URL-encoded parts in the form header.payload.signature. One detail worth remembering is that a JWT is signed, not encrypted. Anyone who holds it can read it, so secrets never belong inside one.</p><h2><strong>Authentication: from passwords to passkeys</strong></h2><p><strong>Passwords</strong> are a shared secret. You know it, and the server stores a copy of it in hashed form. That is the root problem: shared secrets get reused across sites, typed into fake login pages, and leaked when a server is breached.</p><p><strong>Multi-factor authentication (MFA)</strong> adds a second proof:</p><ul><li><p><strong>One-time codes</strong> from SMS or an authenticator app. Better than a password alone, but a fake site can ask for the code too and relay it in real time.</p></li><li><p><strong>Push notifications.</strong> Convenient, but attackers can spam prompts until a tired user taps Approve.</p></li><li><p><strong>Hardware security keys.</strong> The strongest of the three, because the key checks which site it is talking to.</p></li></ul><p><strong>Passkeys</strong> take that last idea and make it mainstream. This is passwordless sign-in: there is no password to type, reuse, or steal. A passkey is a <a href="https://www.w3.org/TR/webauthn/">FIDO2 / WebAuthn</a> credential built on public-key cryptography:</p><ol><li><p>When you register, your device creates a key pair for that one website. The private key stays on your device, and the site receives only the public key.</p></li><li><p>When you sign in, the site sends a random challenge. You unlock the device with a fingerprint, your face, or a PIN, and the device signs the challenge.</p></li><li><p>The site checks the signature with the public key it already has.</p></li></ol><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Ai4w!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Ai4w!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 424w, https://substackcdn.com/image/fetch/$s_!Ai4w!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 848w, https://substackcdn.com/image/fetch/$s_!Ai4w!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 1272w, https://substackcdn.com/image/fetch/$s_!Ai4w!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!Ai4w!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png" width="576" height="546" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/8a381172-67f5-4104-8f72-21bf23064785_576x546.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:546,&quot;width&quot;:576,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Diagram of a passkey sign-in: the website sends a challenge, the device signs it with the private key, the website verifies it with the public key&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Diagram of a passkey sign-in: the website sends a challenge, the device signs it with the private key, the website verifies it with the public key" title="Diagram of a passkey sign-in: the website sends a challenge, the device signs it with the private key, the website verifies it with the public key" srcset="https://substackcdn.com/image/fetch/$s_!Ai4w!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 424w, https://substackcdn.com/image/fetch/$s_!Ai4w!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 848w, https://substackcdn.com/image/fetch/$s_!Ai4w!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 1272w, https://substackcdn.com/image/fetch/$s_!Ai4w!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8a381172-67f5-4104-8f72-21bf23064785_576x546.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><em>Signing in with a passkey. The private key and your fingerprint never leave the device.</em></p><p>This design resists phishing for two reasons. There is no shared secret to steal, because the server holds only a public key. And each passkey is bound to the real site&#8217;s domain, so the browser will not offer it to a look-alike site.</p><p>Passkeys come in two flavors. <strong>Synced passkeys</strong> are backed up and copied across your devices by Apple, Google, Microsoft, or a password manager, which makes recovery easy. <strong>Device-bound passkeys</strong> never leave one device, such as a hardware security key, and suit administrators and other high-risk accounts. The <a href="https://fidoalliance.org/white-paper-fido-authentication-for-moderate-assurance-use-cases/">FIDO Alliance</a> describes both as highly phishing resistant, with different trade-offs between assurance and recovery.</p><p>One more idea completes the picture: <strong>adaptive (risk-based) authentication</strong>. The IdP looks at context, such as a new device, an unusual location, or a sensitive action, and asks for stronger proof only when the risk is higher.</p><h2><strong>Who runs identity today</strong></h2><p>You rarely build an identity provider yourself. You pick one, and the main choices fall into two camps.</p><p><strong>Hosted services</strong> run the IdP for you:</p><ul><li><p><strong><a href="https://learn.microsoft.com/en-us/entra/identity/">Microsoft Entra ID</a></strong> (formerly Azure AD): the natural choice wherever Microsoft 365 is already in use.</p></li><li><p><strong><a href="https://www.okta.com/">Okta</a></strong>: a vendor-neutral platform known for its large catalog of ready-made app integrations.</p></li><li><p><strong><a href="https://auth0.com/">Auth0</a></strong>: owned by Okta since 2021 and aimed at developers who add customer login to their own apps.</p></li><li><p><strong><a href="https://cloud.google.com/identity">Google Cloud Identity</a></strong>: identity for organizations built around Google Workspace and Google Cloud.</p></li><li><p><strong><a href="https://aws.amazon.com/cognito/">Amazon Cognito</a></strong>: customer sign-in for applications that live on AWS.</p></li></ul><p><strong><a href="https://www.pingidentity.com/">Ping Identity</a></strong> sits in between. It offers cloud services as well as software you run yourself, which suits large enterprises with hybrid or on-premises needs.</p><p><strong>Self-managed</strong> means you run the software. <a href="https://www.keycloak.org/">Keycloak</a> is the best-known open-source option and has been a <a href="https://www.cncf.io/projects/keycloak/">CNCF incubating project</a> since 2023. It is free, speaks OIDC, OAuth 2.0, and SAML 2.0, and can pass logins on to other identity providers. You can adapt it at three levels: configuration, themes, and code extensions.</p><p>The trade-off is control against effort. With a hosted service, someone else handles upgrades, uptime, and security patches, and you pay per user and accept the product&#8217;s limits. With Keycloak, you control the data and the behavior, but the database, the upgrades, and high availability become your job.</p><p>Protocols rarely decide the choice. All of these providers issue OpenID Connect and OAuth 2.0 tokens to your applications, and all of them work with SAML 2.0. Amazon Cognito is the partial exception: to your app it is an OpenID Connect provider, and it uses SAML only on the other side, to accept logins from an outside identity provider.</p><p>CERN shows how far the self-managed route can go. It runs three separate Keycloak installations for development, QA, and production, and keeps all of its production services in a single realm. There are roughly 14,000 of them, according to the July 2026 CERN presentation <a href="https://indico.cern.ch/event/1678348/contributions/7063020/attachments/3314358/5932219/The%20Many%20Faces%20of%20Authentication%20and%20Authorisation%20at%20CERN.pdf">The Many Faces of Authentication and Authorisation at CERN</a> (PDF). The lesson I took from that design: you do not need a separate realm for every team or application.</p><p>Running Keycloak myself taught me three practical things:</p><ul><li><p><strong>Inherited roles are hidden by default.</strong> A user&#8217;s Role mapping tab lists only directly assigned roles until you clear Hide inherited roles, so real permissions can be wider than they look.</p></li><li><p><strong>One client, one protocol.</strong> A client speaks either OIDC or SAML. An application that needs both gets two clients.</p></li><li><p><strong>SSO stops at the realm boundary.</strong> A session in one realm does not sign you in to another. That takes identity brokering, where one realm trusts the other as an identity provider.</p></li></ul><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!q_iT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!q_iT!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 424w, https://substackcdn.com/image/fetch/$s_!q_iT!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 848w, https://substackcdn.com/image/fetch/$s_!q_iT!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 1272w, https://substackcdn.com/image/fetch/$s_!q_iT!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!q_iT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png" width="576" height="531" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/cd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:531,&quot;width&quot;:576,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Comparison table of Microsoft Entra ID, Okta, Auth0, Ping Identity, Google Cloud Identity, Amazon Cognito and Keycloak&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Comparison table of Microsoft Entra ID, Okta, Auth0, Ping Identity, Google Cloud Identity, Amazon Cognito and Keycloak" title="Comparison table of Microsoft Entra ID, Okta, Auth0, Ping Identity, Google Cloud Identity, Amazon Cognito and Keycloak" srcset="https://substackcdn.com/image/fetch/$s_!q_iT!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 424w, https://substackcdn.com/image/fetch/$s_!q_iT!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 848w, https://substackcdn.com/image/fetch/$s_!q_iT!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 1272w, https://substackcdn.com/image/fetch/$s_!q_iT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd769974-a6cd-43d3-8b9e-d40c4f9fabaa_576x531.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><em>How the main identity providers compare at a glance.</em></p><h2><strong>Agentic identity: when the &#8220;user&#8221; is an AI agent</strong></h2><p>Everything so far assumes a person at a keyboard or a fixed backend service. AI agents break that assumption. An agent reads your email, opens tickets, and calls other agents, often for a person who is no longer watching.</p><p>Classic identity asks two questions: who are you, and what may you do? Agents add a third: <strong>on whose behalf are you acting?</strong></p><h3><strong>Two modes</strong></h3><ul><li><p><strong>Autonomous.</strong> The agent acts as itself, like a nightly monitoring job. This is ordinary machine-to-machine identity: the client credentials grant, or a workload identity such as <a href="https://spiffe.io/">SPIFFE</a>, which gives software a short-lived cryptographic identity instead of a static secret.</p></li><li><p><strong>Delegated.</strong> The agent acts for a user. The wrong way to do this is impersonation: the agent uses the user&#8217;s own token, and every log entry looks as if the user did it. The right way is delegation, where the token names both the user and the agent.</p></li></ul><p><a href="https://datatracker.ietf.org/doc/html/rfc8693">Token exchange (RFC 8693)</a> standardizes delegation with an act (actor) claim:</p><p>{<br>&#8220;sub&#8221;: &#8220;<a href="mailto:user@example.com">user@example.com</a>&#8220;,<br>&#8220;aud&#8221;: &#8220;orders-api&#8221;,<br>&#8220;scope&#8221;: &#8220;orders:read&#8221;,<br>&#8220;act&#8221;: { &#8220;sub&#8221;: &#8220;shopping-agent&#8221; }<br>}<br>Read it as: &#8220;shopping-agent is acting for <a href="mailto:user@example.com">user@example.com</a>, and may only read orders.&#8221;</p><h3><strong>The chain problem</strong></h3><p>Agents hand work to other agents: user &#8594; agent A &#8594; agent B &#8594; tool. Passing the same token down the chain is tempting and wrong. Every hop carries more permission than it needs, and one stolen token opens everything. The better pattern is a fresh token at every hop, with a narrower audience, fewer scopes, and a shorter lifetime.</p><h3><strong>Where the standards stand</strong></h3><p>None of today&#8217;s finished standards was written for agents. They are general building blocks, reused:</p><ul><li><p>The <a href="https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization">MCP authorization specification</a> treats an MCP server as an OAuth 2.1 resource server and the AI application as an OAuth 2.1 client. It also forbids token passthrough.</p></li><li><p>At the IETF, drafts on identity chaining across domains, transaction tokens, and workload identity (the <a href="https://datatracker.ietf.org/wg/wimse/about/">WIMSE working group</a>) are adapting OAuth to agent scenarios.</p></li><li><p>Vendors are moving too. <a href="https://www.okta.com/blog/product-innovation/cross-app-access-enterprise-ai/">Cross App Access</a>, an open protocol first led by Okta, moves access decisions from individual users to the company&#8217;s identity provider. <a href="https://learn.microsoft.com/en-us/entra/agent-id/what-are-agent-identities">Microsoft Entra Agent ID</a> gives each agent its own identity in the directory, which administrators govern with the same controls they use for people.</p></li></ul><h3><strong>Open challenges</strong></h3><ul><li><p><strong>Accountability and auditing.</strong> When three agents and one human are in the chain, the logs must still show who did what.</p></li><li><p><strong>Consent.</strong> Should each user click Allow, or should the company decide centrally?</p></li><li><p><strong>Revocation.</strong> If a user withdraws permission mid-task, tokens already issued further down the chain keep working until they expire.</p></li></ul><p>Nobody has a complete answer yet, which makes this the most interesting corner of identity to watch.</p><h2><strong>What to take away</strong></h2><ul><li><p><strong>Identity is the perimeter.</strong> Who you are and how you proved it now decides access, not which network you sit on.</p></li><li><p><strong>Authentication and authorization are different jobs.</strong> OIDC answers &#8220;who is this?&#8221; and OAuth answers &#8220;what may this app do?&#8221;</p></li><li><p><strong>Protocols pile up, they don&#8217;t disappear.</strong> LDAP, SAML, and OIDC often run side by side in the same company, and a good IdP translates between them.</p></li><li><p><strong>Passkeys fix the weakest link.</strong> No shared secret means nothing worth phishing.</p></li><li><p><strong>Agents are the next identity problem.</strong> The building blocks exist, but the rules for delegation, consent, and audit are still being written.</p></li></ul><p>Where is this heading? Fewer passwords, shorter-lived tokens, and far more non-human identities than human ones. Identity is turning from a login page into the control plane for everything that touches your data, people and software alike.</p><h3><strong>Further reading</strong></h3><ul><li><p><a href="https://datatracker.ietf.org/doc/html/rfc9700">OAuth 2.0 Security Best Current Practice (RFC 9700)</a></p></li><li><p><a href="https://openid.net/specs/openid-connect-core-1_0.html">OpenID Connect Core 1.0</a></p></li><li><p><a href="https://fidoalliance.org/passkeys/">FIDO Alliance: Passkeys</a></p></li><li><p><a href="https://www.keycloak.org/documentation">Keycloak documentation</a></p></li><li><p><a href="https://datatracker.ietf.org/doc/html/rfc8693">OAuth 2.0 Token Exchange (RFC 8693)</a></p></li><li><p><a href="https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization">MCP authorization specification</a></p></li></ul><p><em>Thanks for reading. If one part of identity still confuses you, leave a comment and tell me which. It may become the next post.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.avild.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Avild Blog! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Technology vacancies surfaced for Azerbaijan]]></title><description><![CDATA[Avild AI Research &#183; 29 September 2026 &#183; Ads collected 28 September 2026]]></description><link>https://blog.avild.com/p/technology-vacancies-surfaced-for</link><guid isPermaLink="false">https://blog.avild.com/p/technology-vacancies-surfaced-for</guid><pubDate>Tue, 29 Sep 2026 06:54:35 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7-n6!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Avild AI</strong> reviewed <strong>3,698 job-ad records</strong> from most used local and global websites in Azerbaijan. Descriptions were available for 3,656. Reviewing titles and duties, then combining clear reposts and employer-name variants, yielded <strong>257 distinct-looking technology listings</strong>. The sample includes some global and remote roles. These are observed ads, not a count of confirmed open positions or a representative survey of all hiring.</p><h2>What the roles show</h2><p>Data, analytics and AI (54), software development (53), and IT infrastructure/support (50) are nearly level in the collected ads. Cybersecurity and IT assurance account for 31; technical business/systems analysis for 17; digital product, design and delivery for 18. One primary category is assigned to each listing, even when its duties cross fields.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!7-n6!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!7-n6!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 424w, https://substackcdn.com/image/fetch/$s_!7-n6!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 848w, https://substackcdn.com/image/fetch/$s_!7-n6!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 1272w, https://substackcdn.com/image/fetch/$s_!7-n6!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!7-n6!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png" width="728" height="449.5" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png&quot;,&quot;srcNoWatermark&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/fbc1b1d2-872b-4e37-8faa-1fc9c6c051c7_2304x1422.png&quot;,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:899,&quot;width&quot;:1456,&quot;resizeWidth&quot;:728,&quot;bytes&quot;:149497,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.avild.com/i/217961735?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ffbc1b1d2-872b-4e37-8faa-1fc9c6c051c7_2304x1422.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!7-n6!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 424w, https://substackcdn.com/image/fetch/$s_!7-n6!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 848w, https://substackcdn.com/image/fetch/$s_!7-n6!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 1272w, https://substackcdn.com/image/fetch/$s_!7-n6!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff05f328e-eec6-48c5-b322-88af2bc196d5_2304x1422.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><h4>The broad labels conceal different kinds of work:</h4><p><br>&#8226; Data, analytics and AI (54): 21 analytics/BI; 19 AI/ML engineering or science; 10 data engineering or architecture; four data governance or leadership.<br>&#8226; Software development (53): 17 back end; 18 general or specialized development; seven lead or architecture; six front end; three full stack; two mobile.<br>&#8226; IT infrastructure/support (50): 18 help desk or field support; 17 systems, database or virtualization; seven networking or connectivity; eight other operations.<br>&#8226; Cybersecurity/IT assurance (31): nine risk or governance; seven IT/security audit; eight security engineering or operations; six application security or testing; one access administration.<br>&#8226; Digital product/design/delivery (18): six product ownership or management; five UX or web design; seven IT or digital project delivery.</p><p><br>Within the cyber and assurance group, risk, governance and audit total 16 of 31. A dedicated SOC Analyst title did not appear in this reviewed group, although some broader jobs describe monitoring, SIEM or incident response. The category is based on responsibilities, not whether a title contains the word &#8220;security.&#8221;</p><h3><br>The technical signals differ by role</h3><p><br>Across the 257 ads, SQL is named in 87, Git in 74 and Python in 69. AI/ML language appears in 60 ads, but an AI mention is broader than an AI-specific job. The role-level pattern is more informative:</p><p><br>&#8226; Data/AI (54): Python 41, SQL 39, Power BI 23, AI/ML 29.<br>&#8226; Software (53): Git 39, Docker 27, CI/CD 25, PostgreSQL 20, React 18.<br>&#8226; Infrastructure/support (50): Linux 23, across work from end-user support to database and network administration.<br>&#8226; Cyber/IT assurance (31): ISO 27001 14, NIST 13, penetration testing 10.<br>&#8226; DevOps/platform (10): Kubernetes 10, Git 9, CI/CD 9, Terraform 6. This is a small base.</p><p><br>The data group is not synonymous with generative AI: 21 of 54 roles are analytics/BI and 10 are data engineering or architecture. Software ads likewise span more than application coding: Git, containers and delivery pipelines recur alongside language and framework names. Technical product and systems-analysis jobs add requirements, APIs, testing, releases and UX work that a developer-only count would miss.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!2hz3!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!2hz3!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 424w, https://substackcdn.com/image/fetch/$s_!2hz3!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 848w, https://substackcdn.com/image/fetch/$s_!2hz3!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 1272w, https://substackcdn.com/image/fetch/$s_!2hz3!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!2hz3!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png" width="1456" height="899" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/e687da33-f43d-493d-a130-47af1ea36825_2304x1422.png&quot;,&quot;srcNoWatermark&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/946ee8ba-5663-4fe8-85b8-03d8f4e76e85_2304x1422.png&quot;,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:899,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:125742,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://blog.avild.com/i/217961735?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F946ee8ba-5663-4fe8-85b8-03d8f4e76e85_2304x1422.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!2hz3!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 424w, https://substackcdn.com/image/fetch/$s_!2hz3!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 848w, https://substackcdn.com/image/fetch/$s_!2hz3!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 1272w, https://substackcdn.com/image/fetch/$s_!2hz3!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe687da33-f43d-493d-a130-47af1ea36825_2304x1422.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><br>Terms also cluster within individual ads. Git occurs with CI/CD in 44 of the 55 CI/CD mentions and with Docker in 44 of the 56 Docker mentions. Python and SQL appear together in 40 ads; Docker and Kubernetes in 33 of the 41 Kubernetes mentions. All 26 Power BI mentions also include SQL. These are co-mentions in ad copy, not proof that each combination is a mandatory requirement or a deployed stack.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!gWp_!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!gWp_!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 424w, https://substackcdn.com/image/fetch/$s_!gWp_!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 848w, https://substackcdn.com/image/fetch/$s_!gWp_!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 1272w, https://substackcdn.com/image/fetch/$s_!gWp_!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!gWp_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png" width="1456" height="967" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png&quot;,&quot;srcNoWatermark&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/fe60c37a-e263-498b-8cf2-44925b468083_2304x1530.png&quot;,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:967,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:150919,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://blog.avild.com/i/217961735?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ffe60c37a-e263-498b-8cf2-44925b468083_2304x1530.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!gWp_!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 424w, https://substackcdn.com/image/fetch/$s_!gWp_!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 848w, https://substackcdn.com/image/fetch/$s_!gWp_!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 1272w, https://substackcdn.com/image/fetch/$s_!gWp_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F186f362f-f0a7-4f58-8cf3-b06b881e8295_2304x1530.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><br><br>At least one of AWS, Azure or Google Cloud appears in 48 ads. Individual mention counts are AWS 34, Azure 29 and Google Cloud 27, with overlap and alternatives in the same descriptions. Google Cloud is especially sensitive to employer mix: 14 of its 27 mentions come from Xsolla listings. The counts cannot establish cloud usage or relative market share.</p><h3><br>Where the ads are concentrated</h3><p><br>The top two named employers contribute 49 of 257 technical records (19%); the top ten contribute 103 (40%). Removing the top two leaves data/AI at 47, infrastructure/support at 44 and software at 38. Software moves from second to third among these families, illustrating the sensitivity of the role mix to large employers. Eleven explicitly bank-named employers account for 57 records, including 18 data/AI, 10 cyber/assurance and 8 technical business/systems analysis roles; that grouping excludes insurers and fintech companies.</p><h4><br>Top 20 named employers by technical listings in this sample</h4><p><br>&#8226; 25: &#304;nnovasiya v&#601; R&#601;q&#601;msal &#304;nki&#351;af Agentliyi.<br>&#8226; 24: Xsolla.<br>&#8226; 9: ABB.<br>&#8226; 7 each: ATB Bank, Bank Respublika, Rabit&#601;bank.<br>&#8226; 6 each: Az&#601;rbaycan Hava Yollar&#305; (AZAL), Bank of Baku, PASHA Bank, Xalq Bank.<br>&#8226; 5 each: Az&#601;rbaycan D&#601;mir Yollar&#305;, Kontakt Home.<br>&#8226; 4 each: Fintech Lab, Intetics, The Flex.<br>&#8226; 3 each: At&#601;&#351;gah S&#305;&#287;orta, Azercell, AzInTelecom, eiGroup, Expressbank.</p><p><br>Twelve employers tie at three records; five are shown alphabetically to keep the list at 20 names. Twelve records lack a usable employer name and are omitted from this ranking.</p><p><br>Method and limits. The cohort was selected through technical title and duty review, including digital product and IT assurance work. General engineering, commercial presales, physical security, teaching and routine functional reporting were excluded unless technical delivery was substantial. Clear cross-source mirrors and repeated employer&#8211;title pairs were combined, so distinct requisitions can be merged and differently worded reposts can survive. Two similarly worded digital loyalty project ads have different role titles and count as two records, without establishing two hires. A named term is counted once per ad and may occur in context or as a preference. 185 technical records have structured posting dates; 173 of these were dated within 30 days before collection, 12 were older, and 72 records have no structured posting date. The oldest dated technical ad is from December 2024. Posting dates do not confirm whether an application is still open, and a single collection cannot demonstrate a rising trend.</p><p></p>]]></content:encoded></item><item><title><![CDATA[The 2030 Tech Job Market, in Two Datasets]]></title><description><![CDATA[What Europe&#8217;s demand model and the World Economic Forum&#8217;s global survey independently agree on &#8212; and where cybersecurity and AI fit in.]]></description><link>https://blog.avild.com/p/the-2030-tech-job-market-in-two-datasets</link><guid isPermaLink="false">https://blog.avild.com/p/the-2030-tech-job-market-in-two-datasets</guid><dc:creator><![CDATA[Ali Mammadzadeh]]></dc:creator><pubDate>Thu, 23 Jul 2026 15:43:35 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!VfYB!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F486aa0c5-66ac-40cf-89ae-08236594768c_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><span>Everyone has an opinion about where tech careers are heading. Fewer people have looked at the actual numbers &#8212; and almost no one lines up two independent, rigorously built datasets to see whether they tell the same story.</span></p><p><span>So we did. We pulled apart two sources that were built completely differently:</span></p><ul><li><p><strong><span>Cedefop&#8217;s Skills Forecast 2026</span></strong><span> &#8212; a model-based projection of European employment out to 2035, grounded in national accounts and labour-force surveys.</span></p></li><li><p><strong><span>The World Economic Forum&#8217;s 2024&#8211;2026 report family</span></strong><span> &#8212; fourteen publications, led by the </span><em><span>Future of Jobs Report 2025</span></em><span>, built from surveys of employers, CEOs and CISOs covering </span><strong><span>1.2 billion jobs</span></strong><span>.</span></p></li></ul><p><span>One is European and mechanical; the other is global and survey-driven. They shouldn&#8217;t necessarily agree. They do &#8212; and the convergence is the story.</span></p><h2><span>1. The headline: churn, not collapse</span></h2><p><span>The most common fear about technology and AI is that they&#8217;ll simply erase jobs. The data says something more precise: </span><strong><span>massive reshuffling, modest net growth.</span></strong></p><p><span>The WEF projects that by 2030, structural change will </span><strong><span>create 170 million jobs and displace 92 million</span></strong><span> &#8212; a </span><strong><span>net gain of 78 million (7%)</span></strong><span>, but a churn equal to </span><strong><span>22% of all jobs studied</span></strong><span>. Nearly one in four jobs is being remade underneath a headline number that looks calm.</span></p><p><span>And the engine of the growth is unambiguous. In percentage terms, the </span><strong><span>fastest-growing roles on the planet are technology roles</span></strong><span>: Big Data Specialists, FinTech Engineers, AI &amp; Machine Learning Specialists, and Software Developers lead the list. The fastest-</span><em><span>declining</span></em><span> roles are clerical and administrative &#8212; bank tellers, data-entry clerks, cashiers, secretaries.</span></p><p><span>Europe&#8217;s numbers tell the same story from the ground up. Using ICT occupations (the closest proxy the European data offers), </span><strong><span>EU-27 employment in IT roles is projected to rise from 6.9 million in 2023 to 9.2 million by 2035 &#8212; a 34% increase</span></strong><span>, with roughly </span><strong><span>4.9 million job openings</span></strong><span> to fill along the way. Two datasets, two methods, one direction: tech demand is structural and rising.</span></p><h2><span>2. Cybersecurity is the standout</span></h2><p><span>If you want a single skill to bet a career on, the data points to one.</span></p><p><span>In the WEF&#8217;s ranking of skills by &#8220;net increase&#8221; in demand, </span><strong><span>networks and cybersecurity ranks #2 in the entire world</span></strong><span> &#8212; behind only AI and big data, and ahead of general technological literacy. Two security roles crack the global top 15 fastest-growing jobs: </span><strong><span>Security Management Specialists (top 5)</span></strong><span> and </span><strong><span>Information Security Analysts</span></strong><span>.</span></p><p><span>Then there&#8217;s the supply side. The cyber workforce faces a global shortage estimated at </span><strong><span>2.8 to 4.8 million unfilled positions</span></strong><span> &#8212; a gap that has </span><em><span>widened</span></em><span> since 2024, with </span><strong><span>two in three organizations</span></strong><span> reporting moderate-to-critical skills gaps. That shortage isn&#8217;t abstract: it creates additional cyber risk for </span><strong><span>70% of organizations</span></strong><span>. And the reports name exactly which roles are hardest to fill: </span><strong><span>threat intelligence analysts, DevSecOps engineers, and identity &amp; access management specialists.</span></strong></p><p><span>The catch worth flagging: the cyber talent gap is deeply uneven. It hits </span><strong><span>small organizations (46% report a shortage) far harder than large ones (29%)</span></strong><span>, and the public sector (57%) and the Global South hardest of all (65% in Latin America, 63% in sub-Saharan Africa).</span></p><h2><span>3. Where in Europe is it easiest to find the work?</span></h2><p><span>Aggregate demand is nice; a job-seeker wants to know </span><em><span>where</span></em><span>. Europe&#8217;s data lets us rank countries by </span><strong><span>hiring intensity</span></strong><span> &#8212; how much hiring happens relative to the size of the existing IT workforce (a demand-side proxy for &#8220;your odds,&#8221; since it doesn&#8217;t account for how many people you compete against).</span></p><p><span>Two patterns emerge:</span></p><ul><li><p><strong><span>Deep ecosystem + brisk hiring</span></strong><span> &#8212; the sweet spot: </span><strong><span>Estonia and Luxembourg</span></strong><span> lead (IT is ~7.5% of all jobs and ~8% of that workforce is hired each year), with </span><strong><span>Denmark, the Nordics, the Netherlands and Lithuania</span></strong><span> close behind. Lots of employers </span><em><span>and</span></em><span> lots of hiring.</span></p></li><li><p><strong><span>Fastest-growing, smaller base</span></strong><span>: </span><strong><span>Romania</span></strong><span> is in a league of its own, with an estimated </span><strong><span>~17% annual hiring rate</span></strong><span> off a rapidly expanding base, followed by Cyprus and Croatia.</span></p></li></ul><p><span>For sheer volume of openings, the big economies still dominate &#8212; </span><strong><span>France, Germany, Poland and Spain</span></strong><span> &#8212; but they&#8217;re also the most crowded.</span></p><h2><span>4. AI&#8217;s double edge</span></h2><p><span>Here&#8217;s where an AI company&#8217;s readers should lean in, because the data resists both the hype and the doom.</span></p><p><span>AI is the single biggest force on this market: </span><strong><span>86% of employers expect it to transform their business by 2030 &#8212; rising to 99% in IT.</span></strong><span> The &#8220;human&#8211;machine frontier&#8221; is shifting fast: the share of work tasks done mainly by humans is projected to fall from </span><strong><span>47% today toward roughly a third by 2030</span></strong><span>.</span></p><p><span>But the reports are clear that the shift is mostly </span><em><span>augmentation</span></em><span>, not wholesale replacement &#8212; nowhere more visibly than in cybersecurity, where AI is easing a burned-out, understaffed workforce:</span></p><ul><li><p><strong><span>88%</span></strong><span> of security teams report time savings from AI.</span></p></li><li><p><strong><span>76%</span></strong><span> of cyber professionals reported exhaustion in 2025; </span><strong><span>55% were understaffed and 53% underfunded.</span></strong></p></li><li><p><strong><span>54%</span></strong><span> say a </span><em><span>skills shortage</span></em><span> &#8212; not the technology &#8212; is the top barrier to adopting AI in security.</span></p></li><li><p><strong><span>92%</span></strong><span> of tech executives say managing AI agents will be a </span><strong><span>non-negotiable</span></strong><span> cyber skill within five years.</span></p></li></ul><p><span>And critically for anyone starting out: in real security operations centres, AI </span><strong><span>cut new-analyst ramp-up time by 50%</span></strong><span> and let junior staff &#8220;contribute earlier in their career.&#8221; The flip side, and the honest warning, comes from the WEF&#8217;s </span><em><span>Global Risks 2026</span></em><span>: a bleaker scenario in which AI eliminates </span><strong><span>up to 50% of entry-level, white-collar jobs</span></strong><span> in the US within five years. The hedge is the same in every dataset &#8212; </span><strong><span>pair fundamentals with AI fluency.</span></strong></p><h2><span>5. The one thing everyone agrees on: skills are the bottleneck</span></h2><p><span>Strip away the sector detail and both datasets land on the same constraint.</span></p><p><span>The WEF calls </span><strong><span>skills gaps the #1 barrier to business transformation (63% of employers)</span></strong><span> &#8212; ahead of culture, regulation and money. Europe&#8217;s productivity research says the same about its own IT sector: </span><strong><span>nearly two-thirds of ICT employers cite skills gaps as a major barrier</span></strong><span>, alongside a &#8220;shortage of digital talent.&#8221;</span></p><p><span>The response is already underway. </span><strong><span>85% of employers plan to upskill their workforce; 70% plan to hire for new skills.</span></strong><span> If the world&#8217;s workforce were 100 people, </span><strong><span>59 would need training by 2030</span></strong><span> &#8212; but </span><strong><span>11 would likely be left behind</span></strong><span> without access to it. Europe&#8217;s IT workforce is visibly moving up the ladder: the share of EU IT jobs held by highly-qualified workers is projected to climb from </span><strong><span>64% in 2015 to about 75% by 2035.</span></strong></p><p><span>Two practical signals for anyone building a plan:</span></p><ul><li><p><strong><span>Experience beats paper.</span></strong><span> Employers rank </span><em><span>evaluating work experience</span></em><span> (81%) far above </span><em><span>requiring a degree</span></em><span> (43%), with short courses and certificates last (14%). Certifications open doors; demonstrated, hands-on work walks through them.</span></p></li><li><p><strong><span>The ladder pays.</span></strong><span> Median wages rise roughly </span><strong><span>37% for each step up the skill ladder</span></strong><span> &#8212; the return on reskilling is real and measurable.</span></p></li></ul><h2><span>What it means, depending on where you stand</span></h2><ul><li><p><strong><span>If you&#8217;re breaking in:</span></strong><span> aim at tech roles, treat cybersecurity as a high-demand bet (target threat-intel, DevSecOps and IAM), build a portfolio of provable work, and get fluent with AI tools early.</span></p></li><li><p><strong><span>If you&#8217;re switching careers:</span></strong><span> the door is open &#8212; employers are actively retraining &#8212; and your prior domain (finance, healthcare, energy) is an asset, since those are exactly the industries demanding cyber skills fastest.</span></p></li><li><p><strong><span>If you&#8217;re already in:</span></strong><span> move up as AI moves in. Learn to manage the machines, shift toward strategy and oversight, and guard against the &#8220;skills atrophy&#8221; that over-reliance on automation can cause.</span></p></li></ul><h2><span>The fine print (because it matters)</span></h2><p><span>Neither dataset is a crystal ball, and we&#8217;d rather you trust the numbers than oversell them. The WEF figures are largely </span><strong><span>survey-based</span></strong><span> and </span><strong><span>forward projections to 2030</span></strong><span> &#8212; they capture what employers </span><em><span>expect</span></em><span>, not measured outcomes. The European figures are a </span><strong><span>demand model</span></strong><span>: they show where the jobs are, but not how many people compete for them, and &#8220;IT occupations&#8221; is a broad proxy that can&#8217;t isolate cybersecurity on its own. Both are best read as </span><strong><span>direction of travel</span></strong><span>, not precise forecasts. Every figure above is drawn directly from the source reports.</span></p><div><hr></div><p><em><span>Sources: Cedefop Skills Forecast 2026; World Economic Forum &#8212; Future of Jobs Report 2025, Global Cybersecurity Outlook 2026, Elevating Cybersecurity 2025, Empowering Defenders: AI for Cybersecurity 2026, Global Risks 2026, and Global Economic Futures (Productivity &amp; Competitiveness in 2030).</span></em></p><p><em><span>We built two interactive companions to this piece &#8212; one mapping which EU country is easiest to find IT work in, and one synthesizing 138 page-cited statistics from the WEF reports. </span></em></p><p><span>&#8212; </span><strong><span>Avild AI</span></strong></p>]]></content:encoded></item></channel></rss>