Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore – Part 1 | Amazon Web Services
An AI agent that updates a ticket or reads a customer record acts for a person, inside applications that person can reach. Your identity team then has to answer a question that per-app OAuth consent and shared service accounts leave open: which agent might act for which user in which application, and how you stop it. Okta Cross App Access (XAA) answers it in your identity provider (IdP). You register the agent in Okta, an administrator approves the applications it might reach, and Okta evaluates policy each time the agent asks to act for a user. In our tests, after an administrator removed a user’s assignment to the agent, Okta refused the agent’s new requests for that user within about 1 second, and tokens already issued expired within 5 minutes.
Amazon Bedrock AgentCoreis a platform to build, connect, and optimize agents at scale, with any framework or model. This...
Copyright of this story solely belongs to aws.amazon.com. To see the full text click HERE