Supported authentication methods in Synthetic Monitoring

Dynatrace Synthetic Monitoring offers various methods for monitoring web applications or API endpoints that require authentication. Read on for an overview of the most common scenarios and the appropriate methods to use.

Browser monitors

The web form (HTML-based) or HTTP authentication methods are supported for single-URL browser monitors and browser clickpaths.

Monitor a web application with web form (HTML-based) authentication

The most common scenario is a webpage with web form (HTML-based) authentication, which requires you to enter a username and password.

Web application with HTML-based authentication

The Web form authentication option is supported for single-URL browser monitors.

  1. From the navigation menu, select Synthetic > Create a synthetic monitor > Create a browser monitor.
  2. In Additional options, turn on Enable global login authentication.
  3. Select the Web form authentication type.
  4. Either use an existing credential from the credential vault (Select credentials) or Create new credentials.
  5. Complete the configuration of your single-URL browser monitor.

Monitor a web application with basic, digest, NTLM, or Negotiate (Kerberos) authentication

If you need to monitor a page with a browser-native dialog box (that is not part of the web application) to authenticate (as in the image below), it's likely that the basic, digest, NTLM, or Negotiate authentication methods are used in the background.

Native browser login dialog box

  1. From the navigation menu, select Synthetic > Create a synthetic monitor > Create a browser monitor.
  2. In Additional options, turn on Enable global login authentication.
  3. Select the HTTP authentication type.
  4. Either use an existing credential from the credential vault (Select credentials) or Create new credentials.

HTTP monitors

HTTP monitors support the basic, NTLM, token, OAuth 2.0, or certificate authentication methods.

Monitor endpoints requiring basic or NTLM authentication

  1. Select Synthetic from the navigation menu > Create a synthetic monitor > Create an HTTP monitor.
  2. Select Add HTTP request and choose the HTTP request type.
  3. In the Additional options of the request, Set authentication/authorization.
  4. Select either Basic authentication or NTLM.
  5. Either use an existing credential from the credential vault (Select credentials) or Create new credentials.
  6. Finish configuring your HTTP monitor.

Monitor endpoints requiring bearer or token authentication

  1. Select Synthetic from the navigation menu > Create a synthetic monitor > Create an HTTP monitor.

  2. Select Add HTTP request and choose the HTTP request type.

  3. In the Additional options of the request, Set additional HTTP headers.

  4. Select Add header.

  5. Fill out the header. For example, set:

    Header name = Authorization
    Header value = Bearer <your-token>

    or

    Header name = Authorization
    Header value = Api-Token <your-token>

  6. Finish configuring your HTTP monitor.

Monitor endpoints requiring OAuth 2.0 authorization

  1. Select Synthetic from the navigation menu > Create a synthetic monitor > Create an HTTP monitor.
  2. Select Add HTTP request and choose the OAth2 authorization request type.
  3. In the Request body (x-www-form-urlencoded), provide the necessary authentication details (grant_Type, scope, client_id, username, and password).
  4. Create an additional HTTP request for the endpoint you need to monitor.
  5. In the Additional options of the second request, Set authentication/authorization.
  6. You can now select the OAuth2 request created above as an authentication method.
  7. Finish configuring your HTTP monitor.

Learn more in our blog post on OAuth 2.0-protected APIs.

Monitor endpoints requiring a client certificate

  1. Select Synthetic from the navigation menu > Create a synthetic monitor > Create an HTTP monitor.
  2. Select Add HTTP request and choose the HTTP request type.
  3. In the Additional options of the request, Add client certificate.
    1. Either use an existing certificate from the credential vault (Select credentials) or Create new credentials.
  4. Finish configuring your HTTP monitor.