AWS bedrock-agentcore medium security documentation change
Summary
Added session binding protection and updated OAuth callback registration flow
Security assessment
Documents unique callback URLs to prevent CSRF/replay attacks and changes setup flow to enforce secure session binding, addressing authorization code interception risks.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-atlassian.md b/bedrock-agentcore/latest/devguide/identity-idp-atlassian.md index eaeb9f42c..979bdba16 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-atlassian.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-atlassian.md @@ -15 +15 @@ Atlassian can be configured as an AgentCore Identity credential provider for out -**Step 1** +###### Note @@ -17 +17,5 @@ Atlassian can be configured as an AgentCore Identity credential provider for out -Use the following procedure to set up an Atlassian 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 Atlassian OAuth2 client first, then return to the Atlassian developer console to register the callback URL once AgentCore Identity has issued it. + +**Step 1: Create the Atlassian OAuth2 client** + +Use the following procedure to set up an Atlassian 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 an Atlassian OAuth2 application and obtain - 4. Enter the following as a callback URL for the app: - - https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback + 4. Leave the callback URL field empty for now — you will add the unique callback URL in Step 3. @@ -40 +42 @@ For more details, refer to [Atlassian’s OAuth 2.0 (3LO) apps documentation](ht -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -55,0 +58,15 @@ To configure Atlassian 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 Atlassian** + +Return to the Atlassian developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the Atlassian 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. + + + +