AWS bedrock-agentcore high security documentation change
Summary
Updated Twitch integration documentation to require registering a unique callback URL per credential provider instead of a fixed URL. Added security note about session binding protection against replay and CSRF attacks.
Security assessment
The change adds explicit security documentation about protection against cross-provider replay and CSRF attacks through session binding. It modifies the implementation to use unique callback URLs, addressing potential authorization code interception vulnerabilities.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-twitch.md b/bedrock-agentcore/latest/devguide/identity-idp-twitch.md index 1a0997790..76a0df10f 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-twitch.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-twitch.md @@ -15 +15 @@ Twitch can be configured as an AgentCore Identity credential provider for outbou -**Step 1** +###### Note @@ -17 +17,5 @@ Twitch can be configured as an AgentCore Identity credential provider for outbou -Use the following procedure to set up a Twitch OAuth2 application and obtain the necessary client credentials for AgentCore Identity. +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 Twitch OAuth2 client first, then return to the Twitch developer console to register the callback URL once AgentCore Identity has issued it. + +**Step 1: Create the Twitch OAuth2 client** + +Use the following procedure to set up a Twitch 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. @@ -27,3 +31 @@ Use the following procedure to set up a Twitch OAuth2 application and obtain the - 4. For the **OAuth Redirect URLs** field, use the following: - - https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback + 4. Leave the **OAuth Redirect URLs** field empty for now — you will add the unique callback URL in Step 3. @@ -44 +46 @@ For more details, refer to [Twitch’s app registration documentation](https://d -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -59,0 +62,15 @@ To configure Twitch 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 Twitch** + +Return to the Twitch developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the Twitch 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. + + + +