Alternative to hard coded username and password in JDBC connection properties

passing hardcoded user name and password in .properties file is not good practice

this has raised questions by information security team

Tags

Data Integration

Accepted answers

All comments

That indeed is not the best practice. Use Certificate based authentication

Quick Links

Can you help?

Unanswered questions

How can i export accuracy metrics from Anaplan Forecaster to Model.
There was an error rendering this rich post.
How to use Client ID and Client Secret for API request directly?
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
New UX Filtering for Hierarchy sibling
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…