If you are unable to log in to Navigator X Web Security Manager (navxwsm), check the following list to make sure that all prerequisites have been met.
1) You must have installed the 10.4.0.1 REST API package (or higher).
2) The WSM REST API listener must be active with Basic Authentication.
Note: If using https for the web server, the rest API also needs to be using https.
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 Administrator group would be authorized.
4) The URL specified on the navxwsm must be correct. Some customers use a virtual host for the Navigator service which includes a host name and port. That cannot be used here since this is a different port.
5) Be sure you are using the same user and password that you use to log in to Navigator, 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 navxwsm. Verify you can log in, then close this dialog.
- Click GET (Show WGS Info).
- Then click Try it out.
- Then click the blue Execute button.
- 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.