Configuring Security Providers

Create a custom provider configuration file:

$JAVA_HOME/conf/<custom_provider_name>.properties

Example content of such a configuration file:

 
# Add name custom provider jar
--module-path=${PROVIDER_PATH}/<custom_provider_jar>
# The following properties are required to access JDK internal classes from the custom provider
--add-exports=java.base/<package>=<custom_provider_module_name>
--add-opens=java.base/<package>=<custom_provider_module_name>
# The following option allows to access classes from non-modular 3rd party libraries
--add-reads=<custom_provider_module_name>=ALL-UNNAMED
# The following option reads custom security properties (if needed)
-Djava.security.properties=${PROVIDER_PATH}/<security_property_file>

The pattern ${PROVIDER_PATH} can be used in this properties file to refer to the $JAVA_HOME/conf/<custom_provider_name>/ directory.

Create the $JAVA_HOME/conf/<custom_provider_name>/ directory and add the following files which are referred in the properties file:

Start your application with this extra Java launcher option:

 
# In cse you have a single custom provider:
--custom-providers=<custom_provider_name>

# In cse you have multiple custom providers:
--custom-providers=<custom_provider_name_1>,<custom_provider_name_2>

Azul Zulu will read <custom_provider_jar> and <security_property_file> from the directory:

$JAVA_HOME/conf/<custom_provider_name>/