Determining additional authentication factor and implementation
-
The customer needs to determine what additional authentication factor to use for HxGN EAM authentication and is responsible for implementing the authentication of additional factor in Java.
-
The implementation has at least one class, the driver class, which will be invoked by the HxGN EAM runtime authentication module. The full package name of the driver class and every other help class must be unique.
-
Package the driver class (and the other helper classes) into a JAR file with a unique name and plug it in to the runtime. The implementation can communicate with external application for the authentication purpose at runtime.
-
The full package name of the driver class needs to be provided as the value of Install parameter MFACLASS.
Plug the customer implementation in to runtime in the JBoss environment:
-
Drop the JAR file into jboss/shared/lib in the install home
-
A restart of the server is not required if there is no subsequent change to the implementation; otherwise, the server needs to be restarted
Plug the customer implementation in to runtime in the WebLogic environment:
-
Drop the JAR file into depconfig/skeletons/mp_subsystem.ear in the install home
-
A redeploy is required
Turning on MFA:
-
Set install parameter MULTIFAC with value ON to turn on MFA.
-
By default the MFA is turned off.
-
The MFA flag cannot be turned on when SSO is turned on. It is a configuration error if the both are turned on