Software·43,965 discussions

Using Slack SCIM API to provision users via SailPoint IIQ

Locked

Tags: Software

I want to use SailPoint IIQ to provision and de-provision Slack users via Slack SCIM API. Slack SCIM API uses version 1.1. and uses Basic or OAuth for authentication. I have setup a Slack Enterprise account, generated the API key, and the SCIM API call works via Postman or cURL. However, I am unable to setup the Basic Auth or OAuth tokens for authentication. Please help!

Topic

Is SCIM API?

In reply to Using Slack SCIM API to provision users via SailPoint IIQ

Image result for Using Slack SCIM API to provision users via SailPoint IIQ
SCIM, or the System for Cross-domain Identity Management specification, is an open standard designed to manage user identity information. SCIM provides a defined schema for representing users and groups, and a RESTful API to run CRUD operations on those user and group resources.

Re: oauth

In reply to Using Slack SCIM API to provision users via SailPoint IIQ

For cURL https://www.google.com/search?q=curl+oauth might be helpful. I leave it to you to use a comparable search for postman.

[kendramiller.213]

Reply To: Using Slack SCIM API to provision users via SailPoint IIQ

In reply to Using Slack SCIM API to provision users via SailPoint IIQ

Sure, I can help you with that.

To set up Basic Auth or OAuth tokens for authentication, you will need to create a new application in the Slack API. You can do this by following these steps:

Go to the Slack API website.
Click on the “Create New App” button.
Enter a name for your application.
Select the “Development” workspace.
Click on the “Create App” button.
Once you have created your application, you will be able to generate your Basic Auth or OAuth tokens. To generate your Basic Auth token, follow these steps:

Click on the “Basic Auth” tab.
Click on the “Generate Token” button.
Your Basic Auth token will be displayed. To generate your OAuth token, follow these steps:

Click on the “OAuth & Permissions” tab.
Click on the “Create OAuth App” button.
Enter a name for your OAuth app.
Select the scopes that you want your OAuth app to have.
Click on the “Create App” button.
Your OAuth token will be displayed.

Once you have generated your Basic Auth or OAuth token, you can use them to authenticate with the Slack SCIM API. To authenticate with the Slack SCIM API using Basic Auth you will need to include the following headers in your request: apkmircle

Authorization: Basic YOUR_BASIC_AUTH_TOKEN
Authorization: Bearer YOUR_OAUTH_TOKEN

I hope this helps!

• This reply was modified 1 year, 10 months ago by kendramiller.213.
• This reply was modified 1 year, 10 months ago by kendramiller.213.

Slack SCIM API

In reply to Using Slack SCIM API to provision users via SailPoint IIQ

Authentication issues often arise from some form of misconfiguration. Here are some troubleshooting steps:
Basic Authentication:
For Basic Auth, you typically just need your Slack API key. It usually gets base64 encoded and set as an Authorization header in your HTTP request, like:
Authorization: Basic <base64encoded(apiKey+’:’)>
Make sure you have followed the above format correctly. Sometimes the issue might just be as simple as a misplaced ‘:’ or incorrect base64 encoding.
OAuth Tokens:
OAuth tokens work a bit differently. After the initial setup of your OAuth application in Slack, you typically need to go through an authorization flow where a user approves the app, and then you get an access token back.
Ensure that you have set up OAuth correctly within Slack, and the OAuth app has the necessary scopes to perform user provisioning and de-provisioning operations.
Make sure the redirect URI in your OAuth app configuration matches the one in your SailPoint IIQ setup. This is a common source of OAuth issues.
SailPoint IIQ Configuration:
Since your call is working via Postman/cURL, the issue may lie within your SailPoint IIQ configuration. Make sure the application or connector you’ve set up in SailPoint IIQ for Slack SCIM API has the correct authentication details and follows the necessary format. Check your connector configuration in SailPoint to ensure you’ve followed their standards for SCIM setup.
Lastly, it might be beneficial to look at logs within SailPoint IIQ and Slack to help pinpoint where the error is occurring. If none of these work, consider reaching out to SailPoint Support for more detailed assistance.
I hope this gives you a good starting point! Good luck!

[Author]

Replies