The Slack connector allows you to connect Slack with One Identity Starling enabling you to take advantage of the features and products available with Starling Connect that complement and enhance the services provided by Slack.

Slack is a cloud-based platform, where users can create and maintain multiple dedicated and organized spaces to allow team members to effectively communicate with each other in a seamless manner.

Connector Configuration

Slack connector requires customer consent to retrieve resource details using REST APIs. Currently, the Slack connector supports the configuration of a single tenant connector only.

Supervisor configuration parameters

To configure the connector, following parameters are required:

• Connector name

• Client Id for the app

• Client Secret of the app

• Target URL (Cloud application's instance URL used as target URI in payload - Example: https://api.slack.com/scim/v1/)

• Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details).

Supported objects and operations

Users

Table 302: Supported operations for Users

Operation	VERB
Create User	POST
Get User	GET
Get Users	GET
Update User	PUT
Delete User	DELETE

Groups

Table 303: Supported operations for Groups

Operation	VERB
Create Group	POST
Get Group	GET
Get Groups	GET
Update Group	PUT
Delete Group	DELETE

Mandatory fields

This section lists the mandatory fields required to create a User or Group.

User

• userName

• emails.value

Group

• displayName

The user and group mappings are listed in the tables below.

Table 304: User mapping

SCIM Parameter	Slack parameter
id	id
userName	userName
name.givenName	name.givenName
name.familyName	name.familyName
name.honorificPrefix	name.honorificPrefix
displayName	displayName
nickName	nickName
emails[].value	emails[].value
emails[].primary	emails[].primary
addresses[].streetAddress	addresses[].streetAddress
addresses[].locality	addresses[].locality
addresses[].region	addresses[].region
addresses[].postalCode	addresses[].postalCode
addresses[].country	addresses[].country
phoneNumbers[].value	phoneNumbers[].value
phoneNumbers[].type	phoneNumbers[].type
phoneNumbers[].primary	phoneNumbers[].primary
profileUrl	profileUrl
title	title
userType	userType
password	password (Write-only and never returned)
preferredLanguage	preferredLanguage
locale	locale
timezone	timezone
active	active
groups[].value	groups[].value
groups[].display	groups[].display
roles[].value	roles[].value
roles[].primary	roles[].primary
photos[].value	photos[].value
photos[].type	photos[].type
extension.costCenter	extension.costCenter
extension.department	extension.department
extension.division	extension.division
extension.employeeNumber	extension.employeeNumber
extension.organization	extension.organization
extension.manager.managerId	extension.manager.value
meta.created	meta.created

Groups

Table 305: Groups mapping

SCIM parameter	Slack parameter
id	id
displayName	displayName
members[].value	members[].value
members[].display	members[].display
meta.created	meta.created

Connector limitations

• Create User operation can create only Active users in the target application. Update User operation can be used to make the user Inactive.
• You cannot create a new user or update the name of an existing user using the name of an existing user or channel.
• The email id provided in the user name field during the User Create operation will automatically be converted to a user name according to the target application standard.
• There is no endpoint available for Roles and any string value can be assigned as a Role of a User. However, the number of strings that can be assigned as a Role of a User has been limited to maximum one.
• Last Modified Date is not returned in meta of Users and Groups.
• Target system supports only soft delete of users. Users deleted using soft delete will still be accessible to read, update and delete.

• Error 429 occurs when the requests from a SCIM client exceed the SCIM API rate limit of the Slack target application.

• The special characters used in userName are converted to underscore in Create User and Update User operations.

• User Name is replaced by the Nick Name when it is passed in a Create User and Update User request.