Connection using Authorization Code

Feedback Documentation Feedback Connectivity Documentation Feedback
1

Sign in to Identity Security Cloud and create a new OAuth client. Go to Admin > Global > API Management > New.

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/servicenow/service_catalog/help/integrating_service_catalog/conn_auth_code.html
2

Has anyone been able to follow these instructions and get the application to work?

I see that Step 11 says " Select authorization_flow as the OAuth Authorization flow method to be used to obtain the access token to call the REST API." but authorization_flow does not exist, so i am using authorization_code. Does this part of the instructions need updated?

Then in following Step 12, i enter the name of the OAuth App from within SailPoint API Management. But this does not seem to work. We get an error on the ServiceNow page. The error says:

Cannot connect to SailPoint IdentityNow server. Please contact Administrator. Error Code 001- Check Admin Setup.

If i change this OAuth value for step 12 to the OAuth name as in Step 6, then we get the same error.

Anyone able to assist with getting this to work?
We are currently working this in our Dev and Sandbox environments.

Thanks in Advance ~!

4

Step 7 confuses me. If I log in to ISC as me and create a PAT, then ISC is connecting to ServiceNow as me. Then if i leave the org or switch roles my access in ISC is going to go away and cause the integration to break.

Can someone clarify what is supposed to happen.

5

Does anyone have thoughts on this? Am i missing something?

7

Hi @swcoleman and @masd1! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-5508

8

For step #7, we also used a static Admin user that we have that is not tied to an actual person and will not leave the org. And of course, have it well documented on what the user is doing and where the tie ins occur.

I ended up working with a SP Engineer, and this was found to be a defect at the time.
It ended up requiring me to create an Event Triger then a Workflow to capture anyone but certain individuals to be able to submit the access as this opened the access in the SP GUI as well and we didn’t want that to occur as we were not building out there.

It will be interesting to see what @Pamela and the CONDOCS-5508 result in, if anything different.