Component Authentication Example

To authenticate your component, you must first Create a LoginModule class for the systems your component accesses. Creation and use of loginModule classes is described in the Sun Microsystems LoginModule Developer's Guide and the JAAS Authentication Tutorial.

The FileNet P8 Platform already provides working samples of these classes for the Process and Content Engines. Both of the FileNet-Supplied LoginModule classes are designed to read entries from login configuration files, as described in com.sun.security.auth.login.ConfigFile.html. The JAAS Login Configuration File that the CE_Operations component uses is named taskman.login.config, and this file is installed in one of the following directories:

You must have a LoginContext section for the login configuration contexts that your loginModule will use in your taskman.login.config file. For the CE_Operations component, this is done automatically with your installation, so there is already a LoginContext named "CELogin" in the taskman.login.config file which identifies and locates program module or modules that are used for logins, as follows:

CELogin
{
filenet.vw.server.VWLoginModule required routerurl="localhost:32771/vwrouter";
com.filenet.wcm.toolkit.server.operations.util.CELoginModule required credTag=Clear;

} ;

Notes

For general information on LoginModules and login configuration (login.config) files, you may refer to the following documents: