# Slack
<a name="identity-idp-slack"></a>

Slack can be configured as an AgentCore Identity credential provider for outbound resource access. This allows your agents to authenticate users through Slack’s OAuth2 service and obtain access tokens for Slack API resources.

## Outbound
<a name="identity-idp-slack-outbound"></a>

**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 Slack OAuth2 client first, then return to the Slack developer console to register the callback URL once AgentCore Identity has issued it.

 **Step 1: Create the Slack OAuth2 client** 

Use the following procedure to set up a Slack 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 a Slack OAuth2 application** 

1. Create a Slack application, enter an app name, and choose the development workspace where the app will be built.

1. Open the **OAuth & Permissions** section. Leave the Redirect URLs list empty for now — you will add the unique callback URL in Step 3.

1. Copy the client ID and client secret that Slack issues for your application. You will need them for configuring the provider in AgentCore Identity.

For more details, refer to Slack’s documentation [Sign in with Slack](https://docs.slack.dev/authentication/sign-in-with-slack/).

 **Step 2: Create the AgentCore Identity credential provider** 

To configure the outbound Slack resource provider, use the following:

```
{
        "name": "NAME",
        "credentialProviderVendor": "SlackOauth2",
        "oauth2ProviderConfigInput": {
            "slackOauth2ProviderConfig": {
                "clientId": "your-client-id",
                "clientSecret": "your-client-secret"
            }
        }
    }
```

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 Slack** 

Return to the Slack developer console and add the unique callback URL to your OAuth2 application’s redirect URI list.

1. Sign in to the Slack developer console and open the OAuth2 application you created in Step 1.

1. Add the `callbackUrl` value returned by `CreateOauth2CredentialProvider` to the application’s redirect URI configuration.

1. Save your changes.