# Custom Authentication in Web Services Connector **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** webservice-connector, identity-security-cloud\ **Created:** [October 9, 2025, 2:05pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976 "2025-10-09T14:05:53Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![nadhikari\_identitynow](https://avatars.discourse-cdn.com/v4/letter/n/958977/32.png) [@nadhikari\_identitynow](https://developer.sailpoint.com/discuss/u/nadhikari_identitynow)\ **Post date:** [October 9, 2025, 2:05pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976/1 "2025-10-09T14:05:53Z")
> ## Hello All, I am working on a Web Service connector. We have an entitlement type which uses different credentials than rest of the API endpoints. So, I am trying to use custom authentication. 1. On Connection Settings: 1. I have put Authentication Type: Custom Authentication 2. Base URL for the API endpoints (Same Base URL is used by all API endpoints even if the authentication used is different). 3. API Token - This is used for Account Aggregation and Entitlement Aggregation - Entitlement 1, 4. Client ID and Client Secret - This is used for Entitlement Aggregation - Entitlement 2. 2. Under HTTP Operations: 1. Custom Authentication: 1. Operation Type: Custom Authenication 2. Headers: Content-Type: application/x-www-form-url 3. Body: Form Data: grant\_type: client\_credentials, client\_id: $application.client\_id$, client\_secret: $application.client\_secret$, scope: , resource: 4. Response Information: 1. Success Codes: 200 5. Response Mapping: 1. customaccesstoken: access\_token 2. Group Aggregation - Entitlement 2 1. Operation Type: Group Aggregation - Entitlement 2 2. Context URL: /entitlement2 3. Headers: Authorization: Bearer $application.customaccesstoken$ 4. Response Information: Success Codes: 200 5. Response Mapping: 1. entitlement2\_id: entitlement2\_id 2. entitlement2\_name: entitlement2\_name I have defined Entitlement Type: entitlement2 with entitlement2\_id as eneitlement id and entitlement2\_name as Entitlement Name. However, when I run the entitlement aggregation by selecting specific type: entitlement2, it returns 0 entitlements. Is there any pointer on this? I feel like I am following all the instructions on the connector documentation on custom authentication. However, it is not working as expected. Please let me know if there is any suggestions on how I can fix this. I would really appreciate any help! Thanks, Nischal ---
**Author:** ![Carlatto](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/carlatto/32/4764_2.png) [@Carlatto](https://developer.sailpoint.com/discuss/u/Carlatto)\ **Post date:** [October 9, 2025, 4:54pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976/2 "2025-10-09T16:54:37Z")
I would check the Root Path on the Response Information tab, and the Attribute Paths on the Root Mapping tab of the Group Aggregation - Entitlement 2 HTTP Operation. You wrote: > Response Mapping: > > 1. entitlement2\_id: entitlement2\_id > > 2. entitlement2\_name: entitlement2\_name Is the Attribute Paths actually “entitlement2\_id” and “entitlement2\_name”? or should they be something else like “id” and “name”? ---
**Author:** ![nadhikari\_identitynow](https://avatars.discourse-cdn.com/v4/letter/n/958977/32.png) [@nadhikari\_identitynow](https://developer.sailpoint.com/discuss/u/nadhikari_identitynow)\ **Post date:** [October 9, 2025, 5:08pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976/3 "2025-10-09T17:08:23Z")
Hi Carl, Thank you for the response. My `“/entitlement2”` endpoint returns the result as following in the postman. `[ { "entitlement2_id":"1", "entitlement2_name":"name1"}, ` `{ "entitlement2_id":"2", "entitlement2_name":"name2"}, ` `{ "entitlement2_id":"3", "entitlement2_name":"name3"}` `]` I have blank as root path. I have the attribute mapping as entitmement2\_id: entitlement2\_id and entitlement2\_name: entitlement2\_name. Is there anything I am missing? Again, thank you for your response. Thanks, Nischal ---
**Author:** ![Carlatto](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/carlatto/32/4764_2.png) [@Carlatto](https://developer.sailpoint.com/discuss/u/Carlatto)\ **Post date:** [October 9, 2025, 5:20pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976/4 "2025-10-09T17:20:51Z")
Since your endpoint is giving a response as an Array, try setting your Root Path to: $[\*] ---
**Author:** ![nadhikari\_identitynow](https://avatars.discourse-cdn.com/v4/letter/n/958977/32.png) [@nadhikari\_identitynow](https://developer.sailpoint.com/discuss/u/nadhikari_identitynow)\ **Post date:** [October 13, 2025, 7:38pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976/5 "2025-10-13T19:38:24Z")
Hi Carl, It is still not working for me for some reason. I was trying to see if using before operation to generate token would work. I am able to generate the token and print it in the log. Use the token in log in Postman API to call the /entitlement2 endpoint. However, the connector is not working for some reason. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [December 12, 2025, 7:46pm UTC](https://developer.sailpoint.com/discuss/t/custom-authentication-in-web-services-connector/184976/7 "2025-12-12T19:46:30Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.