Executing a GET operation in an existing WebServices Update Account (PUT) operation

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

Leveraging a WebServices Before Operation rule tied to an Update Account operation that will execute a GET request to search for a user account and extract a value from the response which will then be added to the jsonBody of the main Update Account (PUT) request.

List<String> allowedStatuses = new ArrayList();
allowedStatuses.add( "2**" );
Map header = requestEndPoint.getHeader();

String employeeCodeFilter = "EmployeeCode eq 'ch00009'";
String encodedEmployeeCodeFilter = URLEncoder.encode(employeeCodeFilter,StandardCharsets.UTF_8);

//retrieve the configured Base URL from the Source
String baseUrl = application.getAttributeValue("genericWebServiceBaseUrl");
String fullurl = baseUrl + "/odata/Custodians" + "?$filter=" + encodedEmployeeCodeFilter;

WebServicesClient client2 = new WebServicesClient();
Map args = new HashMap();
args.put(WebServicesClient.ARG_URL,baseUrl);
client2.configure(args);

String response= client2.executeGet(fullurl, header, allowedStatuses);

The final line generates the following error:
sailpoint.connector.ConnectorException: 500 : {"error":{"code":"666666","message":"SW666666-Unknown Sql exception"}} BSF info: Rule - WebServices Before Operation Logging at line: 0 column: columnNo\n\tat

The resulting fullurl value is a valid endpoint that does return the desired data in Postman.

Appreciate any insight on what I need to do differently. Thx

2

The issue likely comes from mismatched URL and base URL in how you’re configuring the WebServicesClient. Check and let me know if this works

3

Thank you Manvitha. The issue ended up being that one of the header elements was a lengthy JSON object and its value needed to be different when executing a GET operation vs POST/PUT and I had not realized that. The incorrect value was causing the endpoint to be rejected.