--- title: Adding Slack to Your PingOne for Enterprise Dock description: Add the Slack application to your PingOne for Enterprise Dock from the application catalog. component: pingoneforenterprise page_id: pingoneforenterprise:pingone_for_enterprise_app_catalog:p14eapps_slack canonical_url: https://docs.pingidentity.com/pingoneforenterprise/pingone_for_enterprise_app_catalog/p14eapps_slack.html revdate: October 4, 2023 section_ids: steps: Steps choose-from: Choose from: result: Result next-steps: Next steps slack-connection-configuration: Slack Connection Configuration steps-2: Steps choose-from-2: Choose from: choose-from-3: Choose from: next-steps-2: Next steps slack-provisioning: Slack Provisioning before-you-begin: Before you begin about-this-task: About this task steps-3: Steps result-2: Result: next-steps-3: Next steps slack-attribute-mapping: Slack Attribute Mapping about-this-task-2: About this task steps-4: Steps choose-from-4: Choose from: next-steps-4: Next steps slack-customization: Slack Customization steps-5: Steps next-steps-5: Next steps slack-group-access: Slack Group Access about-this-task-3: About this task steps-6: Steps next-steps-6: Next steps --- # Adding Slack to Your PingOne for Enterprise Dock Add the Slack application to your PingOne for Enterprise Dock from the application catalog. ## Steps 1. In the PingOne for Enterprise admin console, go to **Applications > Application Catalog**. 2. **Optional:** In the **Search** field, search for the application. 3. Click the **Slack** application line to expand it, and then click **Setup**. 4. On the **SSO Instructions** tab, click **Download** to download the signing certificate. 5. In a separate tab or window, go to [slack.com/admin](https://www.slack.com/admin) and sign on to your Slack account as a team owner. 6. In Slack, go to **Menu > Authentication > SAML authentication > Configure**. 7. From the **SAML provider** list, select **Custom SAML 2.0**. 8. In the **SAML SSO URL** field, enter `https://sso.connect.pingidentity.com/sso/idp/SSO.saml2?idpid=`, replacing *\* with the **IdP ID** field from PingOne. 9. Enter the PingOne for Enterprise signing certificate: 1. In a plain text editor, open the PingOne for Enterprise signing certificate you downloaded in step 4. 2. Copy the contents of the certificate. 3. In Slack, paste the copied certificate contents into the **X.509 Certificate** field. 10. On the **Settings** line, click the button to set single sign-on (SSO) requirements. ### Choose from: * **Required** * **Partially Required** * **Optional** If your users include restricted or single-channel guest accounts, select **Partially Required**. 11. Click **Save Configuration**. ## Result Slack will send a confirmation email to all users, prompting them to connect their Slack accounts to their single sign-on (SSO) accounts. After they confirm, they will be able to SSO into Slack. ## Next steps In PingOne, click **Continue to Next Step**. ## Slack Connection Configuration ### Steps 1. Import the metadata for Slack: #### Choose from: * Click **Select File** to upload the metadata file. * Click **Or use URL** to enter the URL of the metadata. 2. In the **ACS URL** field, replace the *${teamname}* variable with your Slack subdomain. 3. In the **Entity ID** field, enter the entity ID. The default value of `https://slack.com` should work for most configurations. 4. In the **Target Resource** field, enter a URL to redirect the user to after IdP-initiated SSO. 5. In the **Single Logout Endpoint** field, enter a URL for PingOne to send single logout (SLO) requests to. 6. In the **Single Logout Response Endpoint** field, enter a URL for PingOne to send SLO responses to. 7. To add a **Primary Verification Certificate**, click **Browse** to locate and upload a local certificate file used to verify SLO requests and responses coming from Slack. 8. To add a **Secondary Verification Certificate**, click **Browse** to locate and upload a local certificate used to verify SLO requests and responses if the primary certificate fails. 9. Select the **Force Re-authentication** checkbox to require your identity bridge to re-authenticate users with an active SSO session. 10. Select the **Encrypt Assertion** checkbox to encrypt outgoing SAML assertions. 11. On the **Signing** line: #### Choose from: * Click **Sign Assertion** to have PingOne sign outgoing SAML assertions. This is the default option. * Click **Sign Response** to have PingOne sign responses to incoming SAML assertions. 12. From the **Signing Algorithm** list, select an algorithm with which to sign SAML assertions. 13. Select the **Use Custom URL** checkbox to enter a customer URL to launch Slack from the dock. 14. Select the **Set Up Provisioning** checkbox to configure user provisioning to Slack. ### Next steps Click **Continue to Next Step**. ## Slack Provisioning ### Before you begin Ensure that popups are permitted in your browser. ### About this task | | | | - | -------------------------------------------------------------------------------------------------------------------- | | | If you don't need to set up user provisioning, proceed to [Slack Attribute Mapping](p14eapps_slack_attributes.html). | If you selected **Set Up Provisioning** on the **Connection configuration** tab: ### Steps 1. In PingOne, click**Continue to Next Step**. 2. Click **Activate**. #### Result: The **Customer Log In** page appears in a pop-up window. 3. On the **Customer Log In**, page, enter your team name and sign on to the Slack admin console. 4. Click **Authorize**. ### Next steps In PingOne, click **Continue to Next Step**. ## Slack Attribute Mapping ### About this task PingOne will automatically populate required SAML attributes. For Slack, the required attribute is `SAML_SUBJECT`. Map it to your email attribute. Click **Advanced** and from the **Name ID Format to send to SP** list, select **urn:oasis:names:tc:SAML:1.1:nameid-format:persistent**. ### Steps 1. To add an additional optional attribute, click **Add new attribute**. 2. In the **Application Attribute** field, enter the attribute name as it appears in the application. 3. In the **Identity Bridge Attribute or Literal Value** field, choose one of the following: #### Choose from: * To map to the application attribute: Enter or select a directory attribute. * To assign to the application attribute: Select **As Literal**, then enter a literal value. 4. To create advanced attribute mappings, click **Advanced**. Learn more in [Creating advanced attribute mappings](../pingone_for_enterprise/p14e_creating_advaced_attribute_mappings.html). ### Next steps Click **Continue to Next Step**. ## Slack Customization ### Steps * To change the application icon, click **Select image** and upload a local image file. The image file must be: * PNG, GIF, or JPG format * 312 x 52 pixels maximum * 2 MB maximum file size | | | | - | ------------------------------------------------ | | | Images are scaled to 64 x 64 pixels for display. | * To change the name of the application displayed on the dock, in the **Name** field, enter a new name. * To change the description of the application, in the **Description** field, enter the new description text. * To change the category to which the application is assigned on the dock, in the **Category** list, select a category. Learn more in [Creating a custom application category](../pingone_for_enterprise/p14e_creating_custom_application_category.html). ### Next steps Click **Continue to Next Step**. ## Slack Group Access ### About this task The **Group Access** tab shows every user group that you have created. Learn more in [Adding user groups](../pingone_for_enterprise/p14e_add_groups.html). ### Steps * To add a group's access to the application, on the line for that group, click **Add**. * To remove a group's access, on the line for that group, click **Remove**. * When you're finished assigning groups, click **Continue to Next Step**. ### Next steps On the **Review Setup** tab, review your configuration, and click **Finish** to add the application to your PingOne Dock.