AWS bedrock-agentcore high security documentation change
Summary
Added security note about unique OAuth2 callback URLs and restructured setup steps. Changed from static callback URL to provider-specific dynamically generated URL.
Security assessment
The change explicitly addresses security vulnerabilities by implementing unique callback URLs per provider to prevent cross-provider replay and CSRF attacks in OAuth2 authorization flows. The documentation now explains how this protects against specific attack vectors.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-github.md b/bedrock-agentcore/latest/devguide/identity-idp-github.md index dafcab2e9..c8f03494a 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-github.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-github.md @@ -15 +15,3 @@ GitHub can be configured as an AgentCore Identity credential provider for outbou -**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 GitHub OAuth2 client first, then return to the GitHub developer console to register the callback URL once AgentCore Identity has issued it. @@ -17 +19,3 @@ GitHub can be configured as an AgentCore Identity credential provider for outbou -Use the following procedure to set up a GitHub OAuth2 application and obtain the necessary client credentials for AgentCore Identity. +**Step 1: Create the GitHub OAuth2 client** + +Use the following procedure to set up a GitHub 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. @@ -29,3 +33 @@ Use the following procedure to set up a GitHub OAuth2 application and obtain the - 5. Enter the necessary details specific to your application. For authorization callback URL enter the following: - - * `https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback` + 5. Enter the necessary details specific to your application. Leave the **Authorization callback URL** field empty for now — you will add the unique callback URL in Step 3. @@ -50 +52 @@ For more details, refer to Github’s documentation [Creating an OAuth app](http -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -65,0 +68,15 @@ To configure the outbound GitHub 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 GitHub** + +Return to the GitHub developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the GitHub 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. + + + +