Before this feature was introduced in Sematext Cloud, you had to create Browser Monitors and write user journey scripts to monitor an endpoint that requires authentication in any way.
Now, with authentication support for HTTP Monitors, you can do this easily with a couple of clicks, without having to write a script.
Based on the type of authentication required by the monitored endpoint, you have the option to choose between Bearer Access Token and Basic Authentication support.
If you select the Bearer Access Token, before we call the monitored endpoint, we will first fetch the token from the entered access token URL for each run, then pass this token in monitored API requests.
If you select the authentication type Basic Authentication, the entered username and password are passed within each monitor run that connects to your protected APIs.
The authentication support allows you to check the HTTP response codes, the contents of the response body, and errors when an authentication fails and create alerts, while also giving you the ability to monitor the response of an endpoint when a token or authentication credentials were passed successfully.
For more information, please refer to HTTP monitors authentication support.