This is already answered here: http://bugs.kepler.ro/browse/DBCF-119. In short, it is not possible, and if someone has access to the context.xml file, you have bigger security issues.
It is possible to encrypt the password, but you will have to write a custom factory that will decrypt the password on the Tomcat's side, but again, if an attacker has access to your Tomcat, he can decompile your factory class to access the actual db password.
To sum up, restrict the access to your Tomcat/JIRA instance, it's far easier, cleaner and safer way to secure your system.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs