Help Needed – Web SaaS Connector Custom Authentication (Bearer Token) Issue

[hkhandale (Harsh Khandale)]

Hi Team,

I’m working on configuring a Web SaaS Connector where I need to retrieve a Bearer Token from a standard authentication URL provided by the target application.

Authentication URL:

I have configured Custom Authentication in the connector and set only the Base URL under the authentication configuration.

Then, I created a custom HTTP operation for token generation with the following details:

Test Connection:

Despite this setup, I’m still encountering the following error during execution:

[ConnectorError] Response status: 401 – Failed to validate token

Could you please assist me in resolving this issue or let me know if I’m missing anything in the custom authentication flow?

Thanks in advance for your support!

[Chaithu9110 (CHAITHANYA M)]

Hi harsh

[Chaithu9110 (CHAITHANYA M)]

[Chaithu9110 (CHAITHANYA M)]

in response mapping add id and user name

[JackSparrow (Theja C)]

Setting looks good to me. For token generation, can you try with cURL command once? It worked once for us when we are unable to generate token with API command

[sauvee (Edwin Sauve)]

Can you try to give the ‘access_token’ in your configured response mapping a more unique value, and use that as the variable? So something like “accessTokenAppX”.

[hkhandale (Harsh Khandale)]

Thank you, team, for your response. I tried all the suggestions, but eventually, I realized it was a simple mistake on my part. The token I was receiving already included the prefix “Bearer”, but I was still passing it in the header as Bearer $application.accesstoken$. I’ve now corrected it by using just $application.accesstoken$ in the header, since the token already includes “Bearer”.