<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5WR00001uYYLn0AOOkta Classic EngineAdministrationAnswered2026-08-05T18:24:55.000Z2026-07-21T20:41:26.000Z2026-08-05T18:23:46.000Z

Join the Discussion for Ask Me Anything on August 5, 2026: Okta for AI Agents

Join us on Wednesday, August 5, 2026 (9:00 AM – 11:00 AM PT) for an interactive Ask Me Anything (AMA) on Okta for AI Agents—our dedicated identity security solution for non-human identities, machine-to-machine (M2M) architectures, and autonomous workflows! Submit questions starting today through Tuesday, August 4, 2026, by clicking the ‘Answer’ button below.

 

Featured Expert

Brent Arrington – Principal, Product Acceleration Specialist, Okta 

Screenshot 2026-07-20 at 2.45.04 PM 

Why Join?

As AI transitions into autonomous enterprise workflows, 88% of organizations have already experienced AI agent security incidents. Whether you need to discover "shadow AI," eliminate static API keys, or manage dynamic non-human permissions, Brent will be answering your architecture and deployment questions live in this thread. 

 

How to Participate

  • Submit Questions: Ask your questions in this thread starting today through Tuesday, August 4, 2026. 
  • Live Written Q&A: Brent will respond live right here on Wednesday, August 5, 2026, from 9:00 AM – 11:00 AM PT. 
  • Community Rewards: Participating earns you community points and an exclusive event badge! 🎉

👉 To submit a question, click the ‘Answer’ button below!

 

Sample Topics You Can Ask About:

  • AI Agent Discovery: Where are my agents? What can they connect to? What can they do?
  • Onboarding: How to register agents as first-class identities with assigned human accountability.
  • Protecting Connections: Swapping out risky, long-lived static keys for dynamic, short-lived tokens.
  • Lifecycle Governance: How to build automated review paths and use the instant kill switch to freeze a rogue agent.

 

💬 Want more details on this AMA session? Read the full Community Blog Post here --> https://okta-support.pixtulate.com/help/s/blog/a67WR00000O62uBYAR/august-5-ask-me-anything-ask-me-anything-on-securing-ai-agents-now-generally?language=en_US


  • Mihai N. (Okta, Inc.)

    Is Okta for AI Agents available for free trial/integrator orgs?

    • Yes, it is possible to enable Okta for AI Agents on free trial / integrator orgs on a trial basis.

       

      The one caveat is that the org must be running Okta Identity Engine (OIE), not classic engine.  All new/recent free trial/integrator orgs are on Okta Identity Engine by default, but older orgs could still be running classic engine.  You can quickly tell which engine your org is running by checking the version number at the bottom of the screen in the Admin Console.  Versions ending in the letter “E” are running Okta Identity Engine.  Versions ending in the letter “C” are running classic engine, and would need to be upgraded to OIE before Okta for AI Agents would be supported on the org.

       

      There are a few different options for trials of Okta for AI Agents.  I would suggest reaching out to your account team or contacting Okta support to see which option would best suit your needs.

      Expand Post
      • One point of clarification here: You would either need to be an existing Okta customer (so that you have an account team to contact, or would be able to open a ticket with Okta Support), or if you are a prospect in active sales discussions, you can work with your sales rep if you are interested in a POC of Okta for AI Agents.

        Expand Post
  • SomeoneNamed (Customer)

    Does it support any AI agent or are there specific protocols that AI agents has to support to integrate with Okta?

    • There are a number of components to Okta for AI Agents – from detection, registration, governance, and facilitating/securing agent connectivity to resources.  There are no specific requirement/limitations on which Agents can benefit from Okta for AI Agents, but if we focus specifically on securing agent access to resources, there are a couple of things to keep in mind:

        • The Resource Connections secured by Okta for AI Agents are resources external to the agent itself.  So, agents running entirely within the scope of their own application (i.e. never needing to access external systems to complete tasks) would have no need to request access to resources through Okta.  They could still potentially be detected, registered, assigned owners (for accountability purposes), etc., in Okta however.
        • For agents requesting access to external resources through Okta, there are essentially two patterns, at a high level, for the agent to connect to Okta:
          1. Direct connection to Okta as an IDP:  This would most likely apply to first party (built by your developers) agents, or open-source agents, where the agent code itself can be modified to know how to initiate the resource requests directly to Okta.
          2. Connecting via Okta MCP Bridge or Okta’s Agent Gateway:  This pattern would work for any agent capable of being configured to point to an MCP for resource access.  In this scenario, either the Okta MCP Bridge (self-hosted) or the Agent Gateway (Okta-hosted, currently in Research Release) would, in effect, act as the “virtual MCP”.  Agents would point directly to the MCP Bridge or Agent Gateway URL, and all of the resource/tool access would be configured in and brokered through the Bridge or Gateway.

       

      Expand Post
  • I’m hearing a lot about Cross App Access. Is this the same as Okta for AI Agents?

    • No, Cross-App Access is not the same as Okta for AI Agents.  Cross-App Access is a new standard protocol (an extension of the OAuth/OIDC spec) specifically designed for securing Agentic access to resources. 

       

      Okta for AI Agents is a broader product offering for detecting, governing, and securing access to and by AI Agents.  Okta for AI Agents makes use of Cross-App Access as one of the possible mechanisms for connecting agents to resources, but it is not the only mechanism supported, nor is connecting agents to resources the only capability of Okta for AI Agents.

      Expand Post
  • avshch (BCRC)

    Would Okta for AI agents allow us to register Google Gemini AI agent? If so which controls would we gain over Google Gemini?​

    • While you technically could register Gemini as an Agent in Okta for AI Agents, you would likely not gain much in terms of actual controls over Gemini.  From what I have seen in my own use of Gemini is that it operates internally to Google Workspace and does not access resources outside of its own Google Workspace platform.  In such a scenario, registering the agent in Okta for AI Agents would be more about visibility than access control.

       

      Where you would gain access controls would be if the agent needed to connect to resources outside of Google Workspace.

       

      OR, alternately, if Gemini could be configured to access Google Workspace resources via an MCP (i.e. treat Google Workspace as an external resource), then we could broker those resource connections via Okta.  But from what I’m aware, this is not currently possible with Gemini.

      Expand Post
  • Kathy.Tran (Okta, Inc.)

    What are the first steps to migrate our AI agents away from static API keys and over-privileged service accounts?

10 of 25
This question is closed.
Loading
Join the Discussion for Ask Me Anything on August 5, 2026: Okta for AI Agents