Workflow HTTP Request Encryption

[Santhakumar (Shantha Kumar)]

Hi,

I want to encrypt the client secret that i have used in HTTP Request in workflow. However i have used OAuth credentials as Auth Type and it was encrypted in the UI. But when i have checked from API i am able to see the clientSecret there.

Is there any other way to handle this. Also i have searched the community regarding but i can’t find much more.

Thanks,
Shantha Kumar

[Santhakumar (Shantha Kumar)]

Hi All,

As of now it’s ok that the encryption is happening in the UI, but if you have any idea to this pls add your thoughts here.

Thanks

[neeraj99 (Neeraj Nautiyal)]

Hi @Santhakumar
This is weird the secret should be encrypted as well; It should look something like this

$secret.SomeID

This is how it looks on my tenant.

And i have confirmed this as well that for every workflow it is something different $secret.ID even though the secret is used same in all the workflows.

Maybe try creating a new workflow because OOTB sailpoint workflows supports this.

[neeraj99 (Neeraj Nautiyal)]

If it still doesn’t works, best route would be to raise a ticket with sailpoint.

[Santhakumar (Shantha Kumar)]

@neeraj99 It’s look good in the picture you have shown. If you check under formRequestBody it was not encrypted there.

[neeraj99 (Neeraj Nautiyal)]

@Santhakumar

formRequestBody

Can you share the snippet of the code or image? I want to understand which action is it that you have used?

[Santhakumar (Shantha Kumar)]

@neeraj99 I have previously used the Auth type as None and used the POST method to generate the token using the form-data as body format.

After then i have changed it to OAuth does this will affect or it will shows the formRequestBody when we take the WF through API or download the script.

[Santhakumar (Shantha Kumar)]

It got resolved after i have created new workflow from the scratch. Thanks @neeraj99 for the input.