AWS bedrock-agentcore high security documentation change
Summary
Added security note about unique callback URLs and reorganized steps to register callback URL after provider creation.
Security assessment
Explicitly states that unique callback URLs prevent replay/CSRF attacks in OAuth2 flows. Documents security feature protecting authorization-code exchange through session binding.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-notion.md b/bedrock-agentcore/latest/devguide/identity-idp-notion.md index ea92fde31..09dea9f8a 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-notion.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-notion.md @@ -15 +15 @@ Notion can be configured as an AgentCore Identity credential provider for outbou -**Step 1** +###### Note @@ -17 +17,5 @@ Notion can be configured as an AgentCore Identity credential provider for outbou -Use the following procedure to set up a Notion 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 Notion OAuth2 client first, then return to the Notion developer console to register the callback URL once AgentCore Identity has issued it. + +**Step 1: Create the Notion OAuth2 client** + +Use the following procedure to set up a Notion 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. @@ -31,3 +35 @@ Use the following procedure to set up a Notion OAuth2 application and obtain the - 6. On the integration details page, open the **OAuth Domain & URIs** section and add the following as a redirect URI: - - https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback + 6. On the integration details page, open the **OAuth Domain & URIs** section. Leave the redirect URI list empty for now — you will add the unique callback URL in Step 3. @@ -42 +44 @@ For more details, refer to [Notion’s authorization documentation](https://deve -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -57,0 +60,15 @@ To configure Notion 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 Notion** + +Return to the Notion developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the Notion 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. + + + +