Remove Entitlement URL endpoint is missing using Webservice Connector

[jwshin (Jaewon Shin)]

Hi Experts,

I am facing an issue while implementing the remove entitlement operation using the webservice connector.

The API endpoint for removing entitlements receives a list of group type entitlement values, and the endpoint request is repeated for each list item. The URL contains special characters, such as hyphens (e.g., /scim/Groups/123bc-456cf-789gh). Due to this, it seems the URL ends with a comma, causing a 400 Bad Request error.

Exception while updating account. URL:
https://targetsource.com/scim/Groups/4a9207xxx-1xxxf-4exx6-83xx-6490cedxxx1,
Message: 400: Bad Request, HTTP Error Code: 400

The troubleshooting guide recommends setting “skipEncodingDecodingUrl”: “true”
in the source connectorAttributes, but this does not resolve the URL corruption.

Has anyone encountered a similar issue or can offer advice on how to resolve this?

Regards,

[703hardik (Hardik Sharma)]

Hi @jwshin ,

I think there’s a problem with your group-id list.
I’m assuming your list looks like this -

["4a9207xxx-1xxxf-4exx6-83xx-6490cedxxx1","4a9207xxx-1xxxf-4exx6-83xx-6490cedxxx2","4a9207xxx-1xxxf-4exx6-83xx-6490cedxxx3"]

Ensure ID don’t contain the"," and are properly enclosed in double quotes(“xxyxxyx”)

[jwshin (Jaewon Shin)]

Hi @703hardik ,

Provisioning plan payloads where the entitlement attribute requests presented as a list, like below:

Provisioning Plan Example

ACCOUNT REQUEST Modify account: 35516xx8-21xx1-46xyz3-bxxx9e-e18xxxxx1a67

ATTRIBUTE REQUESTS Remove value: 4a9xx5d-1xxf-4xx6-8xxd-649xxxxdb8b1, ad4xxxb1-dxxx7a-4xxb-b7xx9-0axxx19a, 12exxx479-7xxxa-41xxe-96xyz-3c9xxxxxx138

This means the request id itself does not contain commas; it’s just that the list values are connected with commas.

and request url remains comma in the finish lines.

Regards,

[mehuljogi (Mehul Jogadia)]

Hello @jwshin ,

Can you try using %2C instead of , in the URL.

[Abhinov7 (Abhinov Dhonthula)]

Hi,

I believe the remove entitlement operation will be called individually for the list of entitlements. Lets say there are four entitlements to be removed it will be called 4 times. So the “,” wont be the issue,

Try to check CCG logs or provide the payload you are sending. I think the payload is not forming correctly.

-Abhinov

[jwshin (Jaewon Shin)]

Hi @Abhinov7,

To identify the implementation issue, I reviewed the request body content and discovered that escaping some field as double quotes within JSON body.
Thanks for helping identify the problem.