Troubleshooting Authentication Failed error

Troubleshooting Authentication Failed error

Authentication Failure

Authentication failure occurs when the request to a resource is missing or has invalid credentials. 

Check if URL requires authentication

Access the URL in an incognito/private window and check if any pop up asking for credentials is shown. Enter the username and password required to access the URL's resource in the private window. Ensure that you have provided the same credentials in the "Basic/NTLM Authentication" field in URL Monitor's edit monitor page. 
You can also check if the URL needs credentials by accessing it using cURL/Wget. Ensure you do not provide credentials in the command. See if the response code is 401- this means the URL requires authentication.

Form-based authentication

On navigating to the URL in a browser, if a form is shown in which credentials have to be entered, then the URL most likely uses form-based authentication. In such cases, ensure that the URL monitor's "Form Submission Method" is POST and the corresponding payload containing the credentials is configured.
Form-based authentication will be similar to the Applications Manager's login page.

Check User-Agent

Certain servers are designed to fail authentication for requests originating from sources other than browsers. In such cases, edit the User-Agent of the URL monitor. You can get your User-Agent's value from After entering the value in the edit monitor screen, update the URL monitor and poll the monitor a couple of times, and check. 

Special Characters

In rare cases, the presence of special characters in the password may lead to incorrect encryption while storing in the Applications Manager's database. In such cases, create a password without any special characters and update the same in the URL monitor's edit monitor page, update the monitor, and check.

                    New to ADSelfService Plus?

                      • Related Articles

                      • Real User Monitor (RUM) - Troubleshooting

                        If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                      • Microsoft Azure - Troubleshooting on "Authentication Failed" error for Azure Organizational Account mode

                        "Authentication Failed. Access is Denied for the provided Azure Organizational Account Credentials" - Error message upon adding a New Azure monitor using Azure Organizational Account mode. Troubleshooting: Check if the provided User Email & Password ...
                      • Troubleshooting URL Monitor

                        Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...
                      • Troubleshooting Failed Diagnostic Tests

                        This KB is intended for troubleshooting Diagnostic Tests with Failed results. If you encounter any errors displayed in the monitor that prevent the execution of Diagnostic tests, or if there is no data available for Diagnostic Tests, please refer ...
                      • Troubleshooting SSL Handshake Error

                        SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate.  ...