What changed
AWS published a two-part AgentCore pattern using Okta Cross App Access to bind an agent to a signed-in user, exchange short-lived grants and enforce tool policy through AgentCore Gateway and Cedar. In AWS's test setup, removing a user stopped new grants in about one second while issued tokens lasted up to five minutes.
Why it matters
The pattern replaces shared agent service accounts with explicit user-and-agent identity and a measurable revocation window. It also shows that different target applications can have different consent and revocation behavior, so one identity design cannot be assumed to govern every tool.
What to do
Reproduce the sample in a test tenant with two agents and two users, verify default deny, remove a user and a resource connection, measure every issued token's survival, and join IdP, gateway, Cedar and resource logs before adapting the chain to production.
Caveat
The measured timings and authorization behavior reflect AWS and Okta's configured test environment. The snippets are explicitly sample code rather than a complete production solution, and stored OAuth grants for third-party targets can outlive an IdP suspension until separately revoked.