I have a java application that connects to a database.
The user name and password for the database are stored in a properties file.
What is the common practice to avoid storing the password in cleartext in the properties file while still retaining the option to let the user change it?
The main motivation here is to prevent someone looking over the admin’s shoulder and seeing the password while the admin is editing the properties file.
I read here that there’s a built in way to do it in C#.
Knowing java, I don’t expect to find a built in solution but I’d like to hear what other people are doing.
If I don’t find any good choice then I am probably going to encrypt it with a constant password that will be kept in the code. But I’d hate to do it this way because it feels wrong.
Edit Dec 12th 2012
Looks like there is no magic and I must store the password in the code or something similar.
At the end we implemented something very similar to what Jasypt that was mentioned in one of the answers does.
So I’m accepting the Jasypt answer because it is the closest thing to a definite answer.
Jasypt provides the org.jasypt.properties.EncryptableProperties class for loading, managing and transparently decrypting encrypted values in .properties files, allowing the mix of both encrypted and not-encrypted values in the same file.
http://www.jasypt.org/encrypting-configuration.html