<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Agent Gateway on I_AM Fabio</title>
    <link>https://iam.fabiograsso.net/tags/agent-gateway/</link>
    <description>Recent content in Agent Gateway on I_AM Fabio</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 18:40:29 +0200</lastBuildDate>
    <atom:link href="https://iam.fabiograsso.net/tags/agent-gateway/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dust &#43; Okta Agent Gateway: Connect MCP Tools Securely</title>
      <link>https://iam.fabiograsso.net/howto/dust-agent-gateway/</link>
      <pubDate>Sat, 26 Sep 2026 16:00:00 +0000</pubDate>
      <guid>https://iam.fabiograsso.net/howto/dust-agent-gateway/</guid>
      <description>Following my Blueprint Alliance article, this guide turns the role of an Agent Gateway into a concrete configuration example. Connect Dust to MCP servers through Okta, configure user access and Static OAuth, select the tools to expose, and trace requests back to both the agent and its user.</description>
    </item>
    <item>
      <title>Blueprint Alliance: A Shared Architecture for AI Agents</title>
      <link>https://iam.fabiograsso.net/blog/blueprint-alliance-ai-agents/</link>
      <pubDate>Wed, 23 Sep 2026 09:00:00 +0200</pubDate>
      <guid>https://iam.fabiograsso.net/blog/blueprint-alliance-ai-agents/</guid>
      <description>Okta&amp;rsquo;s original agentic enterprise blueprint has grown into the Blueprint Alliance, bringing identity, cloud, AI, data, application and security vendors around a shared reference architecture. Here is what changed, how its four questions shape agent governance, and what architects should test before adopting the model.</description>
    </item>
  </channel>
</rss>
