Webservice source attribute reference is not working

Divya_Kusumula03 · December 6, 2024, 9:16am

Hi ,
We have Webservice connector with Authentication as OAuth 2.0 grant type as password.
Where we need to pass an encoded key in authorization header as shown in image, when we hardcode the value , test connection is working fine, if i add that key in source attributes and added it in encrypted list it is not working and test connection is failing.

Thanks,
Divya

sk8er23 · December 6, 2024, 10:43am

Can you share your workflow request?

liamkokeeffe · December 9, 2024, 5:42pm

Hi Divya,

Did you append the ‘$’ at the end of your source attribute name as well? So the value should look like ‘Basic $application.Encoded_Credentials$’.

Value is cutoff in your screenshot so just wanted to double check.

Thanks,

Liam

liamkokeeffe · December 9, 2024, 5:45pm

Also you may need to suffix the attribute with ‘_CA’. In the web services custom auth documentation, there’s a note there that the source may show some weird behavior if not suffixed appropriately. (https://documentation.sailpoint.com/connectors/webservices/help/integrating_webservices/idn_config_for_custom_authentication.html)

Thanks,

Liam

Divya_Kusumula03 · December 10, 2024, 4:24am

Hi Liam,
I did try both Basic $application.Encoded_Credentials$ and
by adding _CA while creating attribute and tried $application.Encoded_Credentials_CA$ also.
But no luck
Thanks,
Divya

jrossicare · December 10, 2024, 5:51am

Where are you setting Encoded_Credentials variable?

you can try start with lowercase letter and remove the underscore. Not sure if that makes a difference or not

Divya_Kusumula03 · December 10, 2024, 7:55am

Creating it as source attribute and added this key in encrypted list in Source using PATCH

Arshad · December 10, 2024, 12:27pm

@Divya_Kusumula03 , the process usually is that you first make the API call from postman, pull out the curl command which contains the header for authorization which usually looks like this:

curl --location '<your URL>' \
--header 'Authorization: Basic <your encrypted token value>' \

From above, use the <your encrypted token value> to patch it on the source. Ensure that you’re patching Encoded_Credentials_CA under /connectorAttributes/ in your source. Once this is done, go ahead to patch the variable name Encoded_Credentials_CA under /connectorAttributes/encrypted

Let me know if it works?

Also, can you maybe show us how the values inside the /connectorAttributes/encrypted key in your source JSON look like?

Thanks,
Arshad.