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, you need to provide the User-Agent in the URL monitor.
- You can get your User-Agent's value from https://www.whatismybrowser.com/detect/what-is-my-user-agent.
- Go to URL Add monitor page -> Under HTTP(s) configuration section -> In User Agent field -> Enter the User Agent.
- Update the URL monitor and poll the monitor a couple of times, and check.
Still facing issues?
If the problem persists, contact our support team along with the following details:
- A screenshot of the "Add Monitor" page.
- The URL debug tool response for the URL monitor.
- Reproduce the issue and share the latest Support Information File (SIF) from Applications Manager, with the "Print all logs" option enabled. To do this, go to Settings > Logging, and choose "Print all logs".
New to ADSelfService Plus?
Related Articles
Microsoft Azure - Troubleshooting "Authentication Failed. Reason: Host Unavailable" error
"Authentication failed. Reason: Host Unavailable" - Error message upon adding a New Azure monitor and during data collection Troubleshooting: Ensure that the Applications Manager installed server has internet connectivity. The following hosts must be ...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 the RUM Agent configuration 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
When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...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 ...