IdentityNow (IDN) Sensitive Source Headers - API

Does anyone have instructions on how to use the REST API to add a sensitive header into a source? The Web Services document mentions doing this but has no instructions and neither does the API documentation. https://community.sailpoint.com/t5/IdentityNow-Connectors/Web-Services-Source-Configuration-Reference-Guide/ta-p/78511#toc-hId-841347690

Hey @jlazerus

Thank you for your question. I wanted to let you know that we have reached out to the original author of the article for input on your question. They are located abroad and will be online again early Monday; we will try to get that answer for you as quickly as we can. Hang tight!

1 Like

@jlazerus

I reached out to the original author of the article, and he is working with engineering to update the original compass article to include the information you need. I’ll keep you posted when it’s updated.

2 Likes

Great, thank you very much!

1 Like

For any sensitive information, keep it in password or client_secret or any encrypted field and refer it using $application.password$ in anywhere in source config end point.

if you make get source call and check the json, there is a key which says encrypted and in values you would see attribute names, anything from that list can be used.

2 Likes

That worked perfectly. Thank you so much!

1 Like

A post was split to a new topic: Encrypt OAuth Headers in Web Service Source