AgentCore Identity now accepts plain OAuth 2.0 discovery URLs

Amazon Bedrock AgentCore Identity no longer needs OpenID Connect discovery. Teams with OAuth 2.0-only authorization servers can now use them for inbound and outbound auth.

what changed

On 13 November 2026 AWS said Amazon Bedrock AgentCore Identity now supports OAuth 2.0 authorization server discovery URLs. Before this, it accepted only OpenID Connect (OIDC) discovery URLs.

The change covers two places. One is inbound JWT authorization, where a caller proves who it is before it reaches your agent. The other is outbound OAuth credential providers, where your agent gets a token to call another service.

Some authorization servers speak OAuth 2.0 but not OIDC. They publish their metadata at a different well-known path, so AgentCore could not use them. Now it can.

The feature is available in every AWS Region where AgentCore is available. AWS lists no extra charge.

why it matters

This matters most to teams whose identity provider is OAuth 2.0 only. That includes some internal authorization servers and some software-as-a-service providers. Until now they needed a workaround, such as a proxy that added OIDC metadata, or they could not use AgentCore Identity at all.

Fewer workarounds means fewer custom parts to secure. A proxy that fakes OIDC metadata is one more place where trust can break.

The page does not say anything about changes to token handling or scopes. This is only about how the server’s metadata is found.

what we would do

  • List the authorization servers your agents use today. Mark any that are OAuth 2.0 only.
  • If you built a metadata proxy only for AgentCore, try the new discovery URL in a test account and plan to remove the proxy.
  • Read the AgentCore guides for the inbound JWT authorizer before you change a live setup.
  • After the switch, test that a token from the wrong issuer or with the wrong audience is still refused.

sources

Drafted with Claude from the linked sources, reviewed by us.