When LMI is upgraded to 6.1.0 or 6.1.1 and after the advanced features are enabled in the system settings page, the corresponding web UI pages for advanced features load up empty by appearing as a blank white page. This can be due to multiple reasons. 

Cause 1: SSL Certificates:

Starting with LMI version 6.1.0 the web UI for advanced features is handled by llwebapp engine. The webnode initiates an internal authentication with the native Tomcat engine. When the authentication between these nodes fail due to an internal SSL certificates issue, blank pages for advanced features are displayed in the UI. See KB 000034811 for resolution and more information on what causes the issue and how to fix it.

Cause 2: Password Characters:

When advanced features are enabled, the llwebapp node uses simple authentication behind the scenes. This authentication is a secondary authentication layer that occurs automatically when accessing advanced feature pages. For this process the default admin account is used by llwebapp on behalf of the user. When the admin account password contains a certain group of special characters the authentication fails when that password is passed from Tomcat to llwebapp. An indication of that would be that the users should see the following error in the /loglogic/logu/webapp/logs/llweb.log file:

 application="logu",systemId=" ",nodeId="webapp-0000000000",sourceNodeId=" ",targetNodeId=" ",type="ERROR",tenant=" ",domain=" ",sourceIP="  ",targetIP=" ",actor=" ",logger="console",sourceUser=" ",targetUser=" ",id=" ",msg="SyntaxError: Unexpected token ~     at Object.parse (native)     at parse (/loglogic/logu/webapp/node_modules/body-parser/index.js:64:17)     at /loglogic/logu/webapp/node_modules/body-parser/index.js:174:18     at IncomingMessage.onEnd (/loglogic/logu/webapp/node_modules/body-parser/node_modules/raw-body/index.js:117:7)     at IncomingMessage.g (events.js:199:16)     at IncomingMessage.emit (events.js:129:20)     at _stream_readable.js:908:16     at process._tickCallback (node.js:355:11)"

Although the error is generic and can appear for different things, a corresponding error should be seen in the /loglogic/tomcat/logs/logapp.log file as follows:
 

 685 [http-nio-443-exec-5] ERROR Error.jsp - java.lang.NullPointerException         at org.apache.jsp.jsp.error.Error_jsp._jspService(Error_jsp.java:445)         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:438)

This article helps explain multiple reasons as to why the advanced feature pages are empty after the users turn them on after an upgrade. This article also provides fixes to multiple causes.

Users must have the admin privileges to the UI and should have the ability to login as toor into the CLI. Users must be running a valid configuration to enable Advanced features with supported platform and system resources.

For the 2nd cause described above, the only way to fix the issue is to reset the admin account password. To do that, login as admin in the web UI, click the 'User' icon from the top right corner, and choosing the 'Change Password' option.



Once the password is changed, issue the following command: $ mtask -s engine_lldaemon restart. This will then restart all the advanced feature related engines. Reloading the UI should then fix the issue with blank pages.

List of special characters not supported:

 " \ : # (7 consecutive special characters)

Note: In the above example the last line indicates the 7 consecutive special characters. It indicates usage of 7 non-alphanumeric characters consecutively within the password. This includes any and all non-alphanumeric characters and not just the ones we do not support as listed above.

The above are the only special characters that we have identified to have an issue with the simple authentication. If the admin password doesn't contain these above special characters then the issue will not be related to the password itself. 

Note: This issue has been fixed in 6.2.0 version of LMI and users upgrading directly to that version of LMI will no longer need to change the password to remove those special characters.