How to Override Java Security Configuration per JVM Instance


Lately I encountered a configuration tweak I was not aware of, the problem: I had a single Java installation on a Linux machine from which I had to start two JVM instances - each using a different set of JCE providers. A reminder: the JVM loads its security configuration, including the JCE providers list, from a master security properties file within the JRE folder (JRE_HOME/lib/security/, the location of that file is fixed in the JVM and cannot be modified. Going over the documentation (not too much helpful, I must admit) and the code (more helpful, look for, for example here) reveled the secret.


It all starts within the default file provided with the JVM, looking at it we will find the following (somewhere around the middle of the file)
# Determines whether this properties file can be appended to
# or overridden on the command line via

If the overridePropertiesFile doesn’t equal to true we can stop here - the rest of this article is irrelevant (unless we have the option to change it – but I didn’t have that). Lucky to me by default it does equal to true.

Next step, the interesting one, is to override or append configuration to the default file per JVM execution. This is done by setting the '' system property to point to a properties file as part of the JVM invocation; it is important to notice that referencing to the file can be done in one of two flavors:
  1. Overriding the entire file provided by the JVM - if the first character in the' value is the equals sign the default configuration file will be entirely ignored, only the values in the file we are pointing to will be affective
  2. Appending and overriding values of the default file - any other first character in the property's value (that is the first character in the alternate configuration file path) means that the alternate file will be loaded and appended to the default one. If the alternate file contains properties which are already in the default configuration file the alternate file will override those properties.
Here are two examples
# Completely override the default file content
# (notice the *two* equal signs) 

# Append or override parts of the default file
# (notice the *single* equal sign)

Be Carefull

As an important configuration option as it is we must not forget its security implications. We should always make sure that no one can tamper the value of the property and that no one can tamper the alternate file content if he shouldn't be allowed to.


Anonymous said…
Interesting, would it work in conjunction with "-Djava.endorsed.dirs" so that I can have my bouncycastle provider jar outside of jre/lib/ext directory?
Eyal Lupu said…
I cannot remember if the endorsed folder is supported for JCE providers - but if so I don't see a reason why you cannot combine the two.
The best is probably to give it a try
Anonymous said…
It works with -Djava.ext.dirs:

Naresh said…
For some reason, I cannot get this to work. That is, override a property by specifying it in a custom properties file and providing the location via the parameter.

Keep getting the default value specified in file.

I couldn't get this to work in JDK 1.6_32, 1.7.0_25, 1.7.0_40.
Eyal Lupu said…
Make sure you are setting the property (-D) before the main class name.
equestions said…
Eyal, My purpose is really to eliminate overriding. So I plan to change that the default 'true' value to 'false'. For local connections that is sufficient to prevent overriding of system properties. However, that does not work for remote connections using RMI. Any advice with respect to RMI? Thanks!
Unknown said…
This comment has been removed by a blog administrator.

Popular posts from this blog

New in Spring MVC 3.1: CSRF Protection using RequestDataValueProcessor

Hibernate Exception - Simultaneously Fetch Multiple Bags

Hibernate Derived Properties - Performance and Portability