Skip to main content
Top
Review meshIQ Products (G2.com)

Troubleshooting meshIQ Web Security Manager Login Issues

If you are unable to log in to meshIQ Web Security Manager (navxwsm in version 10/secure in version 11), check the following list to make sure that all prerequisites have been met. 

1) For version 10, you must have installed the 10.4.0.1 REST API package (or higher).  For AutoPilot SU34.4 or higher and version 11, REST support is part of the core platform services and does not require a separate package. 

2) The WSM REST API listener must be active with Basic Authentication.

mceclip2.png

Note: If using https for the web server, the rest API also needs to be using https.

mceclip0.png

To verify the REST service is active.  If you have curl installed, do the following command from the WGS server system command line 

curl -X GET "http://localhost:8019/rest/v1/nodes"

If you configured it for https, then use that here.  This should return an error that you are not authorized.  Any other error such as not reachable or invalid certificates will need to be investigated. 

Without curl, use telnet to verify the port is active (telnet localhost 8019)

3) The user logging in must belong to one of the groups listed on in the authorized REST groups. In the example below, only users in the Administrators group would be authorized.

mceclip3.png

Note that with new installations that user Admin may not be part of Administrators by default. Only user Administrator is in Administrators group and able to configure security. 

4) The URL specified on the Security Manager login screen must be correct.  Some customers use a virtual host for the meshIQ service which includes a host name and port.  That cannot be used here since this is a different port.

mceclip4.png

 

5) Be sure you are using the same user and password that you use to log in to meshIQ components, not the Apache-based id used for apodwsm. 

6) Try connecting directly to the WSM REST API using a web browser:

  • Connect to the WSM REST interface using http://your-server:8019/wsm/v1/api-docs, substituting your WSM REST host.
    • If you cannot connect to the REST interface using your hostname, try connecting using the associated IP address.
    • if you cannot connect using IP, check firewalls and other settings. Access to the REST interface, is required.  If you were able to connect at step 2 with curl, you can also try confirming with curl if the desktop system has it.
  • Click the Authorize button and log in with the same user as you use for web security manager. Click Authorize and then close this dialog. Note, no user validation is done at this point, only stored.

 

  • Click GET Server-groups (Search Server Groups).

  • Then click Try it out.

mceclip7.png

  • Then click the blue Execute button.

mceclip8.png

  • This should return a valid response similar to the one below.  If not, use the error provided to verify that the REST API configuration is correct.