REST API Monitor - FAQS

REST API Monitor - FAQS

What to Do When Basic Authentication Fails in REST API Monitor:

When Basic Authentication fails in the REST API monitor, follow these steps to troubleshoot and resolve the issue:
  1. Verify Credentials: Ensure the credentials provided in Applications Manager (username and password) are correct.
  2. Test Authorization Header: Try manually sending the username and password in the Authorization request header to verify the credentials.
  3. BASE-64 Encoding:
    1. To include credentials in the header, you need to encode the username and password in BASE-64 format. For example, if the username is admin and the password is test, the BASE-64 encoded value of admin:test is YWRtaW46dGVzdA==.
    2. Provide the base-64 encoded value in Custom HTTP(s) headers field in REST API monitor as "Authorization_sep_BASIC YWRtaW46dGVzdA==".
    3. After adding the credentials to the Custom HTTP(s) headers, test the API again to verify that the credentials pass successfully.
Notes
In Basic Authentication, the client first makes a request without credentials. If the server responds with a 401 Unauthorized status, the client retries with credentials. However, some server configurations close the connection after a 401 response if no credentials are sent initially, causing Basic Authentication to fail. In such cases, Custom HTTP(s) headers should be used to send the credentials directly in the request to bypass this issue.

                  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 the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                    • Service Now Event Integration using Webhook / Rest API Action

                      Steps to perform in Service Now 1) Login to your ServiceNow Instance(dev*****133.service-now.com) 2) Search for the Rest API Explorer and open it 3) In the Rest API Explorer page choose the Namespace and API Name with the proper API version. For ...
                    • REST API Monitor Troubleshooting Guide

                      Whether you're adding a new REST API monitor or troubleshooting an existing one, the following steps can help resolve common issues. Troubleshooting 4xx Error Codes (e.g., 401, 403) Check Request Configuration: Verify that the correct HTTP method ...
                    • OpenShift Monitoring in Rest API Mode

                      For the OpenShift monitor, data collection when carried out using SSH mode sometimes results in timeout exception due to the presence of large amount of data to be collected. To avoid this, an enhancement has been made and now data collection will ...
                    • How to get ISP and Region data in Real User Monitor?

                      The default setting of the Real User Monitor does not display ISP and region data for the end user. To obtain the data, you have the option to use a third-party Geolocation API. Currently, RUM exclusively supports APIs that provide responses in JSON ...