AWS bedrock-agentcore high security documentation change
Summary
Added security note about unique OAuth2 callback URLs preventing replay/CSRF attacks. Restructured steps: 1) Create X client without callback URL 2) Create credential provider to get unique URL 3) Register URL with X.
Security assessment
Explicitly documents that unique callback URLs prevent cross-provider replay and CSRF attacks in OAuth2 authorization flows. This addresses security vulnerabilities by binding sessions to specific providers.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-x.md b/bedrock-agentcore/latest/devguide/identity-idp-x.md index 21a5bd3cc..895d4b486 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-x.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-x.md @@ -15 +15,3 @@ X can be configured as an AgentCore Identity credential provider for outbound re -**Step 1** +###### Note + +AgentCore Identity issues a unique OAuth2 callback URL for each credential provider you create. The unique callback URL enables session binding, which protects the OAuth2 authorization-code exchange against cross-provider replay and CSRF-style attacks by ensuring an authorization response can only be redeemed against the specific credential provider that initiated it. Because the URL is unique per provider, you won’t know it until **after** you call `CreateOauth2CredentialProvider`. Create your X OAuth2 client first, then return to the X developer console to register the callback URL once AgentCore Identity has issued it. @@ -17 +19,3 @@ X can be configured as an AgentCore Identity credential provider for outbound re -Use the following procedure to set up a X OAuth2 application and obtain the necessary client credentials for AgentCore Identity. +**Step 1: Create the X OAuth2 client** + +Use the following procedure to set up an X OAuth2 application and obtain the necessary client credentials for AgentCore Identity. You will register the redirect URI in Step 3, after AgentCore Identity issues the unique callback URL. @@ -41,3 +45 @@ Use the following procedure to set up a X OAuth2 application and obtain the nece - 11. Under **App Info** enter the following as the callback URL: - - https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback + 11. Under **App Info** , leave the callback URL field empty for now — you will add the unique callback URL in Step 3. @@ -62 +64 @@ For more details, refer to [X’s OAuth 2.0 documentation](https://docs.x.com/fu -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -77,0 +80,15 @@ To configure X as an outbound resource provider, use the following: +The [CreateOauth2CredentialProvider](https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_CreateOauth2CredentialProvider.html) response includes a `callbackUrl` field. This URL is unique to this credential provider and looks like: `https://bedrock-agentcore.us-east-1.amazonaws.com/identities/oauth2/callback/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX`. Save this value for the next step. + +**Step 3: Register the unique callback URL with X** + +Return to the X developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the X developer console and open the OAuth2 application you created in Step 1. + + 2. Add the `callbackUrl` value returned by `CreateOauth2CredentialProvider` to the application’s redirect URI configuration. + + 3. Save your changes. + + + +