AWS Security ChangesHomeSearch

AWS bedrock-agentcore high security documentation change

Service: bedrock-agentcore · 2026-06-04 · Security-related high

File: bedrock-agentcore/latest/devguide/identity-idp-onelogin.md

Summary

Updated OneLogin configuration to require unique callback URLs and added security explanation

Security assessment

Explicitly mentions the unique callback URL prevents cross-provider replay and CSRF attacks by binding authorization responses to specific providers. This directly addresses OAuth security vulnerabilities related to token interception and replay attacks.

Diff

diff --git a/bedrock-agentcore/latest/devguide/identity-idp-onelogin.md b/bedrock-agentcore/latest/devguide/identity-idp-onelogin.md
index e83486a44..90a977b64 100644
--- a//bedrock-agentcore/latest/devguide/identity-idp-onelogin.md
+++ b//bedrock-agentcore/latest/devguide/identity-idp-onelogin.md
@@ -15 +15 @@ OneLogin can be configured as an AgentCore Identity credential provider for outb
-**Step 1**
+###### Note
@@ -17 +17,5 @@ OneLogin can be configured as an AgentCore Identity credential provider for outb
-Use the following procedure to set up a OneLogin 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 OneLogin OAuth2 client first, then return to the OneLogin developer console to register the callback URL once AgentCore Identity has issued it.
+
+**Step 1: Create the OneLogin OAuth2 client**
+
+Use the following procedure to set up a OneLogin 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.
@@ -29,3 +33 @@ Use the following procedure to set up a OneLogin OAuth2 application and obtain t
-  5. On the page for the app, go to the **Configuration** tab and add the following as a redirect URI:
-    
-        https://bedrock-agentcore.region.amazonaws.com/identities/oauth2/callback
+  5. On the page for the app, go to the **Configuration** tab. Leave the redirect URI list empty for now — you will add the unique callback URL in Step 3.
@@ -42 +44 @@ Use the following procedure to set up a OneLogin OAuth2 application and obtain t
-**Step 2**
+**Step 2: Create the AgentCore Identity credential provider**
@@ -60,0 +63,15 @@ To configure OneLogin 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 OneLogin**
+
+Return to the OneLogin developer console and add the unique callback URL to your OAuth2 application’s redirect URI list.
+
+  1. Sign in to the OneLogin 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.
+
+
+
+