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-…

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 name…

IdentityNow (IDN) Sensitive Source Headers - API

Identity Security Cloud (ISC) ISC Discussion and Questions

colin_mckibben (Colin McKibben) Split this topic November 8, 2022, 7:03pm 7

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

Topic		Replies	Views
Encrypt sensitive parameters in the Source configuration ISC Community Knowledge Base rules , identity-security-cloud	0	532	October 26, 2023
Storing sensitive data in workflows ISC Discussion and Questions workflows , identity-security-cloud	4	316	May 25, 2024
Add Encrypted attributes in the Source so that I can use those in the before and after operation rule ISC Discussion and Questions rules , identity-security-cloud	7	603	September 24, 2023
Encrypt OAuth Headers in Web Service Source ISC Discussion and Questions webservice-connector	1	434	July 19, 2023
There currently is no mechanism to secure data in an HTTP request. If you put sensitive information in the headers, like secrets and tokens, it will be output to the logs ISC Discussion and Questions workflows , apis , identity-security-cloud	7	551	July 19, 2023

IdentityNow (IDN) Sensitive Source Headers - API

Related topics