AWS bedrock-agentcore high security documentation change
Summary
Updated Salesforce OAuth2 setup procedure to use unique callback URLs per credential provider instead of a fixed URL. Added security note about session binding protection and restructured into three steps.
Security assessment
The change explicitly addresses security vulnerabilities (cross-provider replay and CSRF attacks) by implementing unique callback URLs with session binding. The documentation now explains how this security mechanism protects authorization-code exchanges.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-salesforce.md b/bedrock-agentcore/latest/devguide/identity-idp-salesforce.md index 2f1808cd8..a637ca3c1 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-salesforce.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-salesforce.md @@ -15 +15 @@ Salesforce can be configured as an AgentCore Identity credential provider for ou -**Step 1** +###### Note @@ -17 +17,5 @@ Salesforce can be configured as an AgentCore Identity credential provider for ou -Use the following procedure to set up a Salesforce 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 Salesforce OAuth2 client first, then return to the Salesforce developer console to register the callback URL once AgentCore Identity has issued it. + +**Step 1: Create the Salesforce OAuth2 client** + +Use the following procedure to set up a Salesforce 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. @@ -23,3 +27 @@ Use the following procedure to set up a Salesforce OAuth2 application and obtain - 2. Enable and configure the OAuth settings for the application, providing the following as the callback URL: - - * `https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback` + 2. Enable and configure the OAuth settings for the application. Leave the callback URL field empty for now — you will add the unique callback URL in Step 3. @@ -44 +46 @@ For more details, refer to Salesforce’s documentation [Define an OpenID Connec -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -59,0 +62,15 @@ To configure the outbound Salesforce 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 Salesforce** + +Return to the Salesforce developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the Salesforce 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. + + + +