![]() The Recommended and Reasonable approach is to have the password Encrypted. Control who know the password of tomcat user (or) who have SUDO privileges and make sure they are the best people to hold the fort.ĭespite doing everything, All these workarounds, Your System is still prone to RISK as long as someone can read the password as Clear Text.Have Auditing on who is viewing the file or copying the file.Setup ACL (Access Control List) for that file and Directory, With the help of setfacl and getfacl commands in Linux.It can be done easily with the chmod command in linux chmod 600 context.xml Make sure you restrict the file permission of the context.xml (or) all the configuration files associated with tomcat under the $CATALINA_HOME/conf/* by restricting access to the Group and others.These are the list of Steps you can do at an instant basis to Secure your Context.xml and DataSource Password. SecureTomcatJDBC in Action – Video Guide.How to Make Sure the New DataSource is working or docked properly?.The Sample Context.xml with SecureTomcatDataSourceImpl Factory.So what is the Difference between The Regular DataSource and SecureTomcatJDBC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |