Securely Connecting to a Secondary Database in ISC JDBC Provisioning Rule

[amishra25 (Ajeet Mishra)]

Hi Experts,

I am working on a JDBC provisioning rule in IdentityNow and have a requirement to fetch attributes from a secondary database. How can I securely connect to this database without hardcoding the username and password in a Rule? Specifically, I want to:

Establish a connection to the secondary database.
Retrieve specific attributes for provisioning.
Ensure credentials are stored securely.

Are there best practices, examples, or documentation for securely managing database credentials in ISC for this use case?

[Gopi2000 (Gopi S)]

You can encrypt the password within the connector parameters, and inside the rule, you can use application.{specific attribute} to fetch the value from the connector during execution.

String userName = (String) application.get(“User Name”);
String password = (String) application.get(“Password”);

If you’re going to add any custom attributes you can do that too, refer to the below doc

Add Encrypted attributes in the Source so that I can use those in the before and after operation rule

Hi Team I have a requirement to make an additional API call to different system in my before rule and wanted to save those credentials on the source in custom attributes as encrypted. I am not able to find any relevant article. I tried patching the source with Attributename_CA but its not encrypting those. Any Suggestions