AWS bedrock-agentcore high security documentation change
Summary
Added security note about unique OAuth2 callback URLs enabling session binding to prevent replay/CSRF attacks. Restructured steps to require creating credential provider first to obtain unique URL before configuring Zoom.
Security assessment
Explicitly mentions protection against cross-provider replay and CSRF-style attacks through session binding via unique callback URLs. Provides concrete security mechanisms.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-zoom.md b/bedrock-agentcore/latest/devguide/identity-idp-zoom.md index 8c2f665c3..7be8cfad6 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-zoom.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-zoom.md @@ -19 +19,3 @@ You can only configure a Zoom OAuth2 application as either a user federation or -**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 Zoom OAuth2 client first, then return to the Zoom developer console to register the callback URL once AgentCore Identity has issued it. @@ -21 +23,3 @@ You can only configure a Zoom OAuth2 application as either a user federation or -Use the following procedure to set up a Zoom OAuth2 application and obtain the necessary client credentials for AgentCore Identity. +**Step 1: Create the Zoom OAuth2 client** + +Use the following procedure to set up a Zoom 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. @@ -33,3 +37 @@ Use the following procedure to set up a Zoom OAuth2 application and obtain the n - * In the **OAuth Information** section, for both the OAuth Redirect URL and OAuth Allow Lists sections, use the following as the redirect URL for the application: - - https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback + * In the **OAuth Information** section, leave the OAuth Redirect URL and OAuth Allow Lists empty for now — you will add the unique callback URL in Step 3. @@ -52 +54 @@ For more details, refer to [Zoom’s integration documentation](https://develope -**Step 2** +**Step 2: Create the AgentCore Identity credential provider** @@ -67,0 +70,15 @@ To configure Zoom 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 Zoom** + +Return to the Zoom developer console and add the unique callback URL to your OAuth2 application’s redirect URI list. + + 1. Sign in to the Zoom 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. + + + +