Help With the Web Service Connector Configuration

Identity Security Cloud (ISC) ISC Discussion and Questions
1

I am configuring a Web Service Connector and need guidance on setting up authorization. I have the following details:

  • Base URL
  • API Key and Secret
  • In Postman, I am able to fetch data successfully by passing the API Key and Secret in the headers with Content-Type: application/json.

Based on this, how should I configure the connection in the Web Service Connector?

1 Like
2

If you plan to use WS connector, then use the OAUTH 2.0, grant type Client Credentials and use the information you have. I am assuming that’s what you are using with POSTMAN.

3

What @sunnyajmera said is good guidance.

You will need to decide which connector you will use.

Direct Connector:

SaaS Connector: Integrating SailPoint and Web Services SaaS

From there, check the " Connecting SailPoint with Web Services" sections for where to set the values you need to connect.

4

Getting these error @gmilunich
We have detected an error from the managed system.

Error Received:
Exception occurred in Test Connection. Error: Exception occurred while generating access token: Unable to generate access token. Response returned: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target SAME ERROE=R

1 Like
5

hi team
now i solve the issue now i am getting zero accounts while aggregation but accounts is present

1 Like
6

Glad to see that you have the operation configured. If you could add what worked for you to resolve that, it would help others who happen upon this topic later.

To help you further, we will need to know the following:

  • Which connector you are using? Direct or SaaS?
  • Do you have a Test Connection Operation set up and is it working?
  • Do you have the HTTP Account Aggregation Operation configured with the same information as Postman?
  • Have to reviewed the full documentation for the connector to make sure you’ve configured everything?
  • Have you reviewed the logs to see if there are any errors/warnings?
  • What steps have you taken to debug this already?
7

i have configured sass connector now i am getting issue while accoount aggregation response map also i have done the account aggregation showing zero accounts scanned

9

@Chaithu9110 It is considered poor etiquette to tag people like this in the response. The users here are other developers with their own day jobs that volunteer to answer questions. It is also the weekend, where most people are off. There is no SLA for providing answers on the forum and no guarentee that you will get one.

It is also poor etiquette to privately message people in chat to try and get faster help unless they offer their services.

If you have an issue that is time sensitive, it is recommended that you contact SailPoint Customer Service/Professional Services to get the support that you need.

Thank you for mentioning that you are using the WebService SaaS connector and reiterating the new issue that you are having with not getting accounts. If you could review the additional questions from my previous post and try some of those items and report back what you found, that would be a good start. The likely cause is going to be a mis-configuration, such as a missing parameter on the request, a missing schema for parsing the response, or something else along those lines if your request is not generating an error.

10

Hi Chaithanya,

To set up the connection, follow these steps:

  1. Configure the Base URL and Authentication:
  • In the Connection settings, set the Base URL.
  • Choose a valid Authentication method:
    If you have an API key and secret -
    • If you have an API token, select API Token authentication.
    • If you don’t have an API token, select Custom Authentication and save the configuration with only the Base URL.
  1. Configure the HTTP Operation:
  • When testing the connection, pass the API key and secret in the request headers.
  • Set the context URL as the exact endpoint of the target URL.
  • Example:
    • Full API URL: https://api.xyz.com/users
    • Base URL: https://api.xyz.com/
    • Context URL: users
  1. Save the Changes and Test the Connection.
  • If the connection is successful, proceed with configuring the aggregation HTTP operation following the same steps.
  • Ensure attribute mapping is set according to the JSON response structure.

If you need further assistance, feel free to reach out.

1 Like
11

let me try harsh i will get back to you thanks for the reply