5.8 Troubleshooting

This section helps you troubleshoot issues that might occur when using a non-default authentication method.

5.8.1 An Invalid OAuth2 Request was Received

Issue: Sentinel displays the following error message:

The service may be disabled or an invalid request was made to an active service. Please contact your system administrator. (An invalid OAuth2 request was received.)

Fix: You need to correct one or more settings for the current authentication method. For detailed information, check the osp-sentinel-<date>.log file in the /var/opt/novell/sentinel/log/osp directory.

5.8.2 Invalid Host Header Name or Request URL Domain Name

Issue: Sentinel displays the following error message:

Unrecognized interface. Invalid Host Header Name or Request URL Domain Name.

Fix: Ensure the FQDN is set properly. On the Sentinel server, update the /etc/hosts file with the following:

Sentinel_IP FQDN_Sentinel_server Hostname

Where:

  • Sentinel_IP is the IP address of the Sentinel server.

  • FQDN_Sentinel_server is the FQDN of the Sentinel server.

  • Hostname is the host name of the Sentinel server.

For example:

127.0.0.1 rbpm.mycompany.com rbpm

NOTE:You can use the $hostname command to verify whether the host name is correct.

For detailed information, check the osp-sentinel-<date>.log file in the /var/opt/novell/sentinel/log/osp directory.

5.8.3 Login Redirects to the Standard Login Page

Issue: Sentinel displays the following error message:

Integrated Windows Authentication is not properly configured in your environment. You will be redirected to the standard login page in 5 seconds.

Fix 1: Clear your browser cache and remove all cookies.

Fix 2: If Fix 1 does not work, ensure the Sentinel server time is synchronized with NTP, and then restart the Sentinel server.