Atlassian
Atlassian can be configured as an AgentCore Identity credential provider for outbound resource access. This allows your agents to authenticate users through Atlassian’s OAuth2 service and obtain access tokens for Atlassian API resources.
Outbound
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 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.
To configure an Atlassian OAuth2 application
-
Open Atlassian’s developer console and register for a developer account.
-
Create a new application.
-
Select authorization and next to OAuth 2.0 (3LO) select Configure.
-
Leave the callback URL field empty for now — you will add the unique callback URL in Step 3.
-
Choose Save changes.
-
Select Permissions and choose the permissions relevant to your application.
For more details, refer to Atlassian’s OAuth 2.0 (3LO) apps documentation
Step 2: Create the AgentCore Identity credential provider
To configure Atlassian as an outbound resource provider, use the following:
{ "name": "NAME", "credentialProviderVendor": "AtlassianOAuth2", "oauth2ProviderConfigInput": { "atlassianOauth2ProviderConfig": { "clientId": "your-client-id", "clientSecret": "your-client-secret" } } }
The CreateOauth2CredentialProvider 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.
-
Sign in to the Atlassian developer console and open the OAuth2 application you created in Step 1.
-
Add the
callbackUrlvalue returned byCreateOauth2CredentialProviderto the application’s redirect URI configuration. -
Save your changes.