REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in the REST API monitor?
If Basic Authentication fails in the REST API monitor, follow the steps below to troubleshoot and validate the issue:
- Ensure that the username and password provided in Applications Manager are correct.
- Try manually sending the username and password in the request header to verify the credentials:
- Combine the credentials in the username: password format (Example: admin: test)
- Encode this string in Base64 (Example result: YWRtaW46dGVzdA==).
- Add this encoded value under Custom HTTP(S) Headers using the format: Authorization_sep_Basic <Base64Value> (Example: Authorization_sep_BASIC YWRtaW46dGVzdA==)
- If there are multiple headers, use a hash (#) to separate the headers.
- Perform Test Credential again to verify that the credentials pass successfully.
Note:
In Basic Authentication, a client typically makes an initial request without credentials. If the server responds with 401 Unauthorized, the client retries with credentials.
However, some servers immediately close the connection after a 401 response, causing Basic Authentication to fail. In such cases, sending the credentials directly through Custom HTTP(S) Headers avoids the issue.
2. How do I configure a browser User-Agent in the REST API monitor?
To configure the browser's User-Agent header, follow the steps below:
- Search "My User-Agent" in your browser. The first result will typically display your browser's User-Agent string.
- Add this value under the Custom HTTP(S) Headers field in the format User-Agent_sep_<Value> (Example: User-Agent_sep_Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36)
- If multiple headers are being used, separate them with a hash (#).
- Click on Test Credential to verify the response.
3. How to configure the appropriate Content-Type in the request header?
The Content-Type header tells the target server the format of the request payload. To configure it:
- Select the appropriate Content-Type based on your payload format:
- FORM → application/x-www-form-urlencoded
- Text → text/plain
- XML → application/xml
- JSON → application/json
- Add the header under Custom HTTP(S) Headers using the format Content-Type_sep_<Value> (Example: Content-Type_sep_application/json)
- Perform Test Credential to verify the response.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting guide
If your Real User Monitor has not collected data for an extended period, follow the steps below to troubleshoot the issue. Step 1: Verify the RUM Agent configuration Real User Monitoring requires the RUM Agent to be installed and mapped to ...REST API Monitor Troubleshooting Guide
Whether you're adding a new REST API monitor or diagnosing issues in an existing one, the steps below will help resolve the most common problems. Troubleshooting 4xx Error Codes (e.g., 401, 403) 1. Check Request Configuration Ensure that the ...Self monitor Applications Manager using Real User Monitoring
We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...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 ...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 ...