LDAP - No LoginModules configured for com.appworx.server.ldap.LDAPAppworxAuthentication : null

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When attempting to login as an Applications Manager User that is authenticated using Active Directory, the following error can be seen...

ErrorMsg: AwE-9999 Internal error 
Details: No LoginModules configured for com.appworx.server.ldap.LDAPAppworxAuthentication

Environment

Release : 9.4.x and 9.5.x

Cause

This issue is commonly seen when the Java_mb variable is not set in the sosite file.

Resolution

When implementing Active Directory with Applicaitons Manager the Java_mb variable must be set to define the location of the AM_GSSAPI.conf and krb5.conf files

This step is detailed in documentation Using Active Directory (broadcom.com) as followed...

 

In the sosite file, set the variable Java_mb to indicate the location of the files created in step 1 and 2. The sosite file should then be sourced and the RMI server restarted. In a UNIX sosite file this would be:

export Java_mb="2048m -Djava.security.auth.login.config=$AW_HOME/AM_GSSAPI.conf -Djava.security.krb5.conf=$AW_HOME/krb5.conf"

*Note the 2048 entry is the amount of memory allocated to the Applications Manager java proceses. This should at minimum be set to 2048

 

After restarting running the command ps -ef|grep java should show the parameter noted above as followed...

java -DAGENT=XYZ944 -Xmx3072m -Djava.security.auth.login.config=/home/XYZ/am944/AM_GSSAPI.conf -Djava.security.krb5.conf=/home/XYZ/am944/

java -DAgentMgr=XYZ944 -DAWCOMM=DISABLE -DSTACK=ENABLED -Xmx3072m -Djava.security.auth.login.config=/home/XYZ/am944/AM_GSSAPI.conf -Djava. 

 

 

Additional Information

Please note that there are some instances where having Java_mb in place will still not work correctly if AX_JAVA_OPTIONS is also being used.  In these cases, it's best to remove (or comment out) the AX_JAVA_OPTIONS line from the sosite file.  Then cd to $AW_HOME and run the following:

unset AX_JAVA_OPTIONS
source site/sosite

Then restart the RMI server and attempt the login again. 

We've had a few customers run into problem when using the Java_mb environment variable while also using AX_JAVA_OPTIONS.  Removing AX_JAVA_OPTIONS usually resolves this error to start with; the Java_mb variable also sets memory for java, so you could probably increase it to match what you had for AX_JAVA_OPTIONS as well.