5.6.1 Overview of custom login modules
Custom login modules are a class that is created to perform application user authentication by using modules other than the Cosminexus standard login modules. This class is created by inheriting the LoginModule interface that is the JAAS SPI.
Custom login modules should be stored in the following directories.
-
Windows:
Cosminexus installation directory\manager\modules
-
UNIX:
/opt/Cosminexus/manager/modules
The custom login module directories can be changed by com.cosminexus.admin.auth.custom.modules in ua.conf (the integrated user management configuration file).
The following are notes to be aware of when storing custom login modules.
-
The class in the directory that stores custom login modules is invoked by the custom login module class loader. Thus, it cannot be directly used by the application. To enable the application to directly use this class, specify the directory that stores custom login directories in the add.class.path key in usrconf.cfg (J2EE server option definition file).
-
Always store custom login modules in the form of .class file. Do not store all custom login modules in a JAR file. If a class hierarchy is present, the custom login module directory must have the same class hierarchy structure.
An example is as follows.
- Example: The custom login module class is my.login.MyLoginModule.
Cosminexus-installation-directory
manager
modules
my
login
MyLoginModule.class
-
To use custom login modules in the integrated user management framework, you must set the custom login modules and the classes associated with the custom login modules in the execution environment beforehand. The JAR file format is not supported. Set the bytecode class files.