AWS bedrock-agentcore high security documentation change
Summary
Added security note about unique callback URLs preventing replay/CSRF attacks, restructured setup into 3 steps: create Dropbox client first, then AgentCore credential provider, then register unique callback URL
Security assessment
Explicitly documents session binding to mitigate cross-provider replay and CSRF attacks. Changes enforce security by requiring unique per-provider callback URLs instead of static URL.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-dropbox.md b/bedrock-agentcore/latest/devguide/identity-idp-dropbox.md index b3b557787..d7782eecc 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-dropbox.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-dropbox.md @@ -19 +19,3 @@ Dropbox does not support the M2M/Client Credentials flow. -**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 Dropbox OAuth2 client first, then return to the Dropbox developer console to register the callback URL once AgentCore Identity has issued it. @@ -21 +23,3 @@ Dropbox does not support the M2M/Client Credentials flow. -Use the following procedure to set up a Dropbox OAuth2 application and obtain the necessary client credentials for AgentCore Identity. +**Step 1: Create the Dropbox OAuth2 client** + +Use the following procedure to set up a Dropbox 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. @@ -37,3 +41 @@ Use the following procedure to set up a Dropbox OAuth2 application and obtain th - 7. On the app overview page, open the OAuth2 section and add the following as a redirect URI: - - https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback + 7. On the app overview page, open the OAuth2 section. Leave the redirect URI list empty for now — you will add the unique callback URL in Step 3. @@ -52 +54 @@ For more details, refer to [Dropbox’s OAuth implementation guide](https://deve -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -67,0 +70,15 @@ To configure Dropbox 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 Dropbox** + +Return to the Dropbox developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the Dropbox 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. + + + +