Problem with disable operation in web service connector

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hello,

I am developing a WebService connector and all operations are working as expected, but the enable operation is returning the following error. I have already cloned the source, but the problem persists. I also recreated it from scratch, and the same issue is occurring in the tenant. I created a new source with only the enable and aggregation operations, and the same problem occurs. I don’t have any rules linked to any operations in the connector, and this only happens with the enable. Last week, I created a WebService connector and everything worked fine, but this week this one is showing the error. Has anyone encountered this before?

Errors

Exception occurred while performing ‘Enable’ operation on identity ‘001971’: Error: Error enabling user for native identity ‘001971’.

Thanks,

Enable Account Operation on Web Services Connector Seemingly Broken
2

Hi @rodrigonovo,

Have you tested this operation through Postman to see if it actually works outside of ISC.?

3

Hi @rodrigonovo could you make sure the API URL, the headers (such as Content-Type and any other required headers) and the JSON body are all correctly configured in the Enable operation ?

Also, enable the Webservice loggers to check more details in the CCG logs.

connector.sdk.webservices": "TRACE"

4

I performed the test and it does work, actually. The disable operation is exactly the same as the enabled one — same body, URL, headers, everything exactly the same — and it works normally.

5

I performed the test in the postman and it does work, actually. The disable operation is exactly the same as the enabled one — same body, URL, headers, everything exactly the same — and it works normally. I will put this information and perform new test to see.

1 Like
6

can you share your HTTP operation JSON Body ?

7

Double-check your “Enable” operation configuration,Validate that the JSON/XML payload for the enable call includes all required fields expected by the target system.If the target system returns a non-2xx HTTP response and your connector is not configured to handle it gracefully, SailPoint will throw a generic error like this. Check if you’re receiving a 4xx or 5xx response from the API. Since this worked last week and now fails on all new sources, open a SailPoint support ticket to check for tenant-specific regressions or backend issues, especially if nothing changed in your connector logic.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.