AWS AgentCore Adds OAuth Discovery Support

Resumo

Pixel’s announcement covers AWS adding OAuth 2.0 discovery URL support to Amazon Bedrock AgentCore Identity on November 13. The change supports OAuth-only authorization servers for inbound JWT authorization and outbound OAuth credential providers. It also explains how RFC 8414 metadata URLs differ from OIDC discovery, helping teams verify metadata before rotating client secrets.

DEV Community

AWS Added OAuth Discovery. Don’t Fix a Metadata Error by Rotating Secrets.

A provider setup fails, and the first instinct is to replace the client secret. That can create a second problem while leaving the first untouched. On November 13, AWS added OAuth 2.0 discovery URL support to Amazon Bedrock AgentCore Identity. The practical payoff is compatibility with authorization servers that publish OAuth metadata without OpenID Connect. Before changing credentials, establish whether the integration ever retrieved the right metadata. AI disclosure: This article was generated with AI assistance from the public sources linked below, with automated fact-checking and editorial inspection. It has not been reviewed by Keith. The URL can be wrong before a secret is involved AWS says the update covers inbound JWT authorization and outbound OAuth credential providers. Previously, AgentCore accepted only OIDC discovery URLs, excluding OAuth-only servers that publish metadata at a different well-known path. That is a specific compatibility change, not a promise that every OAuth integration will work without further configuration. The distinction becomes easy to miss when an issuer includes a path. Consider this fictional issuer: https://identity.example/teams Under OIDC Discovery, its metadata location follows this shape: https://identity.example/teams/.well-known/openid-configuration For OAuth Authorization Server Metadata using the default RFC 8414 suffix, the shape is: https://identity.example/.well-known/oauth-authorization-server/teams Notice where teams moved. RFC 8414, published in June 2018, inserts the well-known segment between the host and issuer path; its compatibility notes explain the difference from OIDC’s appended form. Section 3.3 also requires the returned issuer to match the issuer used to construct the metadata request. Those examples illustrate standards behavior, not a report of a failed AgentCore deployment. Use the provider’s documented discovery URL rather than building one by replacing a suffix in an old configuration. A root-level issuer can conceal the path-order difference during a quick test. Keep the failure stage visible For an outbound integration, I would make the setup record show the issuer, discovery URL, selected client authentication method, and last successful configuration check. These are proposed operational fields, not claims about AgentCore’s console interface. Keep secrets and tokens out of that record. Then investigate the observed failure in order. Could the service reach the metadata document? Did it receive usable metadata for the intended issuer? Did the token exchange fail after discovery succeeded? Did the downstream resource reject the resulting request? Each answer points to a different owner and a different corrective action. Rotating a secret belongs to credential troubleshooting when the evidence supports it. It cannot make an incorrectly constructed metadata URL resolve. Likewise, a successful metadata fetch does not demonstrate that a particular member can access a particular application record. The current custom-provider guide describes discovery as automatic endpoint retrieval and also offers manual configuration. It still requires a client ID and client authentication configuration. Discovery reduces configuration work; it does not supply an application’s credentials. There is also a documentation wrinkle worth recording in a rollout ticket. As checked on November 15, the inbound authorizer guide still describes an OIDC-only discovery URL pattern, while the announcement explicitly includes inbound OAuth discovery support. Verify the configuration path you plan to deploy. Do not quietly turn that inconsistency into a copied implementation assumption. Why this matters for a conversational product The relevant connection to my work is the separation of information flows. The AfroTech Guide case study documents an independent community-built public guide and connected AI experience. Approved public records stay separate from private account state and con...
AWS AgentCore Adds OAuth Discovery Support
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …