Circleload275

• Oracle Slack Integration
• Oracle Slack Sso
• Oracle Slack Download
• Oracle Slack Workspace
• Oracle Slack Workspace Url

• Prepare Slack and register your application instance with Oracle CASB Cloud Service for security monitoring.
• When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to.

Slack

Before You Begin

SAN FRANCISCO (Reuters) - Slack Technologies Inc has secured a partnership with Oracle Corp ORCL.N to integrate the tech giant's enterprise software products into the popular workplace messaging.

Introduction

This document describes how to configure Oracle Identity Cloud Service to provide Single Sign-On (SSO) for Slack using SAML.

For accessing the procedures in this document as a video, see Integrating Slack with Oracle Identity Cloud Service.

For accessing the provisioning procedures in this document as a video, see Provisioning Oracle Identity Cloud Service for Slack.

About Slack

Slack is used for cloud-based team collaboration. It is meant for teams and workplaces, and can be used across multiple devices and platforms. It is equipped with robust features that allow users to not only chat one-on-one with associates but also in groups.

After integrating Slack with Oracle Identity Cloud Service:

• Users can access Slack using their Oracle Identity Cloud Service login credentials.
• Users can start Slack using the Oracle Identity Cloud Service My Apps console.
• Admins can assign and revoke user access to the Slack app using the Oracle Identity Cloud Service administration console.

What Do You Need?

• An Oracle Identity Cloud Service account with authorization rights to manage apps and users (Identity Domain Administrator or Application Administrator).
• A Slack account with authorization rights to configure federated authentication.
• Make sure that the email ID of each user in Slack matches the primary email ID of the Oracle Identity Cloud Service account.

Configuring the Slack App in Oracle Identity Cloud Service

Use this section to register and activate the Slack app, and then assign users to the app.

Prerequisite Step

A dedicated team domain is required before you can register and activate the Slack app.

The team domain appears in the Slack login URL: https://<Team_Domain>.slack.com that you received in an email from Slack.

Registering and Activating the Slack App

1. Access the Oracle Identity Cloud Service Administration console, select Applications, and then click Add.

2. Click App Catalog.

3. Search for Slack, and then click Add.

4. In the App Details section, enter your Slack Team Domain, and then click Next.

   Note: This is the team domain value that you obtained while performing the steps in the 'Prerequisite Step' section.

5. Click Download Signing Certificate.

   Tip: Use this file later during the Slack configuration in the 'Configuring SSO for Slack' section.

6. Click Download Identity Provider Metadata. To learn about other methods you can use to access SAML metadata, see Access SAML Metadata.

   Tip: Use this file later during the Slack configuration in the 'Configuring SSO for Slack' section.

7. Click Finish. Oracle Identity Cloud Service displays a confirmation message.

8. Click Activate, and then click Activate Application. Oracle Identity Cloud Service displays a confirmation message.

Assigning Users to the Slack App

1. On the Slack app page in Oracle Identity Cloud Service, select Users, and then click Assign. The Assign Users window appears.

2. Select users that you want to assign to Slack, and then click OK. Oracle Identity Cloud Service displays a confirmation message stating that the Slack app is assigned to the users that you selected.

Configuring SSO for Slack

1. Access Slack using the URL: https://<Team_Domain>.slack.com. The Sign in page appears.

2. Click Enter email and password, and then login as an administrator.

3. Expand the user menu in the upper-left corner, and then select Workplace settings.

4. On the Settings & Permissions page, select the Authentication tab, and then click Change Settings in the SAML Authentication Settings section.

5. On the Configure SAML Authentication page, use the table to update the federated authentication attributes, and then click Save Configuration.

   This table lists the mandatory federated authentication attributes that you must set to complete the SSO configuration.

   Attribute	Value
   SAML 2.0 Endpoint (HTTP)	Enter the Sign-in URL/SSO Endpoint: https://<IDCS-Service-Instance>.identity.oraclecloud.com/fed/v1/idp/sso.
   Identity Provider Issuer	Enter the Entity ID/Issuer URL. Use the metadata file that you downloaded earlier to obtain the Entity ID/Issuer URL. The Entity ID/Issuer URL information is located in the first line of the metadata. See the 'Registering and Activating the Slack App' section.
   Public Certificate	Click edit, and then paste the certificate that you downloaded during the Slack registration in Oracle Identity Cloud Service. See the 'Registering and Activating the Slack App' section.

Verifying the Integration

Use this section to verify that SSO works when initiated from Oracle Identity Cloud Service (IdP Initiated SSO) and Slack (SP initiated SSO).

Verifying Identity Provider Initiated SSO from Oracle Identity Cloud Service

1. Access the Oracle Identity Cloud Services My Profile console using the URL: https://<IDCS-Service-Instance>.identity.oraclecloud.com/ui/v1/myconsole.

2. Log in using credentials for a user that is assigned to the Slack app. Oracle Identity Cloud Service displays a shortcut to Slack under My Apps.

3. Click Slack. The Slack home page appears.

4. On the Slack home page, confirm that the user that is logged in is the same for both Slack and Oracle Identity Cloud Service. The user name is located in the left navigation menu.

   This confirms that the SSO initiated from Oracle Identity Cloud Service works.

Verifying Service Provider Initiated SSO from Slack

1. Access Slack using the URL: https://<Team_Domain>.slack.com. The Sign in page appears.

2. Click Sign in with SAML. You are redirected to the Oracle Identity Cloud Service login page.

3. Log in using credentials for a user that is assigned to the Slack app. The Slack home page appears.

4. On the Slack home page, confirm that the user that is logged in is the same for both Slack and Oracle Identity Cloud Service. The user name is located in the upper-left corner of the page.

   This confirms that SSO that is initiated from Slack works.

Troubleshooting

Use this section to locate solutions to common integration issues.

Known Issues

Slack displays the message, 'Let's Set up your account.'

Cause: The email attribute sent by Oracle Identity Cloud Service during SSO doesn't match any existing user in Slack.

Solution: Ensure that the user that you assign to the Slack app has an account in both Oracle Identity Cloud Service and Slack with the same email address.

Oracle Identity Cloud Service displays the message, 'You are not authorized to access the app. Contact your system administrator.'

Cause 1: The SAML 2.0 integration between the Oracle Identity Cloud Service Slack app and Slack is deactivated.

Solution 1:

• Access the Oracle Identity Cloud Service administration console, select Applications, and then select Slack.
• In the App Details section, click Activate, and then click Activate Application. Oracle Identity Cloud Service displays a confirmation message.

Cause 2: The administrator revokes access for the user at the same time that the user tries to access the Slack app using Oracle Identity Cloud Service.

Solution 2:

• Access the Oracle Identity Cloud Service administration console, select Applications, and then select Slack.
• In the App Details section, select Users, and then click Assign to re-assign the user.

Oracle Slack Integration

Unknown Issues

For unknown issues, contact Oracle Support:

1. Go to https://support.oracle.com.

2. Select Cloud Support, and then sign in with your support credentials.

3. In the Cloud Dashboard, confirm that there are no planned outages in Oracle Identity Cloud Service, and then click Create Service Request.

4. Select Oracle Identity Cloud Service as the service type.

5. Complete your service request.

Here's what happens when you use Slack as a channel for your digital assistant (or standalone skill):

• Slack hosts your digital assistant through the intermediary of a Slack app.
• Users chat with your digital assistant through the Slack app in the Slack user interface.

See Building Slack apps for Slack's developer documentation for Slack apps.

Below are the steps for creating a Slack channel for Digital Assistant.

Step 1: Get a Slack Workspace

To make your digital assistant (or standalone bot) available in Slack, you need to have a Slack workspace available to you where you have the permissions necessary to create a Slack app.

If you don't have such a workspace available to you, you can create your own. See Slack's Create a new workspace page.

Step 2: Create a Slack App

1. Go to Slack's Your Apps page.

2. Click Create an App.

3. In the Create a Slack App dialog, fill in the App Name and Development Slack Workspace fields and click Create App.

   Once the app is created, its Basic Information page appears.

4. Scroll down to the App Credentials section of the page and note the values of the Client ID, Client Secret, and Signing Secret.

   You'll need these credentials when you set up the channel in Digital Assistant.

Step 3: Add OAuth Scopes for the Slack App

You add OAuth scopes for permissions that you want to give to the bot and to the user.

1. In the left navigation of the web console for your Slack app, within the Features section, select OAuth and Permissions.

2. Scroll to the Scopes section of the page.

3. The scopes fall into these categories:

   • Bot Token Scopes
   • User Token Scopes

4. In the Bot Token Scopes section, add the scopes that correspond to the bot-level permissions that you want to allow. The following bot token scopes are required:

   • chat:write
   • im:history
   • users:read

5. In the User Token Scopes section, add the scopes that correspond to the user-level permissions that you want to allow. The following user token scope is required:

   • files:write

Depending on the requirements of your bot, you may need to add other scopes.

Step 4: Add the App to the Workspace

1. Scroll back to the top of the OAuth & Permissions page.

2. Within the OAuth Tokens & Redirect URLs section, click Install App to Your Workspace.

   A page will appear showing what the app will be able to do.

3. At the bottom of the page, click Allow.

Once you have completed this step, you should be able to see the app in your Slack workspace by selecting Apps in the left navigation.

Step 5: Create a Channel in Digital Assistant

1. In Digital Assistant, click Channels in the left menu and then choose Users.

2. Click + Channel to open the Create Channel dialog.

3. Give your channel a name.

4. Choose Slack as the channel type.

5. Fill in the the values for Client ID, Client Secret, and Signing Secret that you obtained when you created your Slack app.

   You can retrieve these values from the Settings page of your Slack app.

6. Click Create.

7. In the Channels page, copy the WebHook URL and paste it somewhere convenient on your system. You’ll need this to finish setting up the Slack app.

8. Click and select the digital assistant or skill that you want to associate with the channel.

9. In the Route To dropdown, select the digital assistant or skill that you want to associate with the channel.

10. Switch on the Channel Enabled control.

Step 6: Configure the Webhook URL in the Slack App

1. In the left navigation of the web console for your Slack app, select Interactivity & Shortcuts.

2. Turn the Interactivity switch ON.

3. In both the Request URL and Options Load URL fields, paste the webhook URL that was generated when you created the channel in Digital Assistant .

4. Click Save Changes.

5. In the left navigation, select OAuth & Permissions.

6. In the Redirect URLs field, click Add New Redirect URL.

7. Paste the webhook URL, append /authorizeV2, and click Add.

8. Click Save URLs.

9. In the left navigation, select App Home.

10. In the Your App’s Presence in Slack section, turn on the Always Show My Bot as Online switch.

11. In the left navigation, select Event Subscriptions.

12. Set the Enable Events switch to ON.

13. In the Request URL field, paste the webhook URL.

    After you enter the URL, a green Verified label should appear next to the Request URL label.

14. Expand the Subscribe to bot events section of the page and click Add a bot user.

15. Click Add Bot User Event and add the following event:

    • message.im
16. If you plan to make the bot available in group chats, also add the following events:
    • app_mention
    • message.mpim
    • message.channels

17. Click Save Changes.

18. In the left navigation, select Manage Distribution.

19. Under the heading Share Your App with Your Workspace, click Add to Slack and then click Allow.

    At this point, you should get the message You've successfully installed your App in Slack.

Step 7: Test Your Bot in Slack

With the Slack channel and messaging configuration complete, you can test your bot (digital assistant or skill) in Slack.

1. Open the Slack workspace where you have installed the app.

2. In the left navigation bar, select the app that is associated with your digital assistant.

3. In the Message field, enter text to start communicating with the digital assistant.

'New' vs. 'Classic' Slack Apps

Starting with version 20.6 of Oracle Digital Assistant, creation of Slack channels is based on an updated OAuth flow in Slack apps. This updated flow enables more granular scopes. The instructions for channel setup in this guide are based on the new OAuth flow.

See https://api.slack.com/authentication/oauth-v2 for details on the updated OAuth flow.

Any existing channels that were created before Digital Assistant 20.6 and that are based on 'classic' Slack apps will continue to work. However, you should consider migrating those classic Slack apps to new Slack apps. See https://api.slack.com/authentication/migration for the details.

Supported Capabilities

Slack channels in Digital Assistant support the following capabilities:

• text (both sending and receiving)
• images (both sending and receiving)
• files (partial support for sending, full support for receiving)
• emojis (partial support for sending, full support for receiving)
• links
• postbacks
• custom properties
• carousel components (but rendered vertically instead of horizontally)
• list components

Message Constraints

Slack channels in Digital Assistant have the following message constraints:

• Text Messages
  • Maximum length of text message: 3000 characters. If the length exceeds 3000, the text is split over multiple messages.
  • Maximum length of text action label: 30 characters
  • Types of text actions allowed: Postback, URL
• Horizontal Cards
  • Supported?: No. Card is layout is converted to vertical.
• Vertical Cards
  • Maximum length of title: 3000 characters
  • Maximum length of description: 3000 characters
  • Maximum length of card action label: 30 characters
  • Maximum number of cards: 100
  • Types of card actions allowed: Postback, URL
  • Types of card list actions allowed: Postback, URL
• Attachment Messages
  • Supported?: Yes
  • Types of Actions Allowed: Postback, URL
• Action Buttons
  • Maximum length of global action label: 30 characters
  • Types of global actions allowed: Postback, URL

Slack Channel Extensions

For Slack channels, you can extend the functionality of System.CommonResponse components with capabilities that are specific to Slack.

You access the extensions by using the channelCustomProperties element in the System.CommonResponse component and setting the appropriate properties. The code has the following format:

Here are the available custom properties for Slack channels:

Here's an example of using the renderActionsAsDropDown custom property.

And here's an example of using the renderActionsAsDropDown custom property with nested properties for postbackActions, cardPostbackActions, and globalPostbackActions.

Oracle Slack Sso

For more general information on channelCustomProperties, see Channel-Specific Extensions.

Slack Dialog Window

You can create a button to invoke a Slack dialog in a System.CommonResponse component. To do so, you set the button's action property to system.openDialog and include a variable named system.dialogPayload. The action metadata should look something like this snippet:

The value of system.dialogPayload is typically set in a custom component, but also can be defined inline or using a System.SetVariable component.

Here is a simple example using a System.SetVariable component:

Oracle Slack Download

When the user submits input in the Slack dialog, the System.CommonResponse component sets the system.dialogSubmitted transition to move to a state that processes the submitted values. The submitted values are stored in context variables with the same name. For a custom component equivalent of the preceding System.SetVariable example, you would need to define the context variables Type, Date and Amount, since those are are defined in dialogPayload.

Oracle Slack Workspace

It is up to you to determine how to process the submitted field values. The System.CommonResponse component does NOT perform any automatic updates of entity values. It only stores the values in context variables. You will typically process these values in a custom component, so you can do additional validations if needed. In its most simple form, you can store the submitted field values in a string variable and then use the System.MatchEntity component to update entity values. Here is an example on how you could use the submitted values to update the expense composite bag entity:

For documentation on other properties and element types that are supported in the Slack dialog payload, see https://api.slack.com/dialogs#top-level_dialog_attributes. The structure of the dialog payload should be identical to the structure described in the Slack documentation.

Oracle Slack Workspace Url