Specifying the location of the configuration file

This topic describes how the Java and .NET frameworks locate the Access Control configuration file.

A sample login configuration file (named Login.conf) is provided in the %ENDECA_CONF%\etc directory ($ENDECA_CONF/etc on UNIX). You can modify this file (including changing the file name) and store it in any directory.

How the Java framework finds the configuration file

In a Java framework, JAAS finds the login configuration file by examining the value of the java.security.auth.login.config property within the Java JVM in which the Access Control System is running. If this property is not set, the system will look for a file named .java.login.config in the home directory of the user who started the JVM.

How you set the java.security.auth.login.config property depends on the specifics of your application server. A common method to specify the configuration file is to use a JVM -Djava.security.auth.login.config command-ine argument, as in this example:

java -Djava.security.auth.login.config=Login.conf weblogic.server

A second method is to edit the JAVA_HOME/jre/lib/security/java.security file and add the name of the login configuration file, as in this Windows example:

# Default login configuration file
login.config.url.1=file:C:/EndecaProjects/SSL/Login.conf

Note that even though the path is on Windows, you must use forward slashes because the path is actually a URL.

Please consult your application server documentation for full details on how to set this property.

How the .NET framework finds the configuration file

The .NET Framework finds the login configuration file by examining the value of a registry setting, which is set by the Endeca installation program to the %ENDECA_CONF%\etc\Login.conf path.