The Crawler extracts the Set-Cookie response header from the login page,
stores that cookie and sends it in a Cookie header when crawling all pages of the website defined in the configuration.
This cookie is only retrieved at the beginning of each complete crawl.
It won’t be renewed automatically if it expires.
The Crawler can interact with your login page in these ways:
With a direct request with the credentials to your login endpoint, like a standard curl command
(fetchRequest).
By emulating a web browser, loading your login page, entering the credentials and validating the login form
(browserRequest).
The crawler supports the OAuth 2.0 Client Credentials Grant flow.
It performs an Access Token Request using the provided credentials,
stores the retrieved token in an Authorization header,
and sends it when crawling all pages of the website defined in the configuration.
This token is only retrieved at the beginning of each complete crawl.
It won’t be renewed automatically if it expires.
Client authentication is performed by passing the client credentials (client_id and client_secret)
in the request body as described in RFC 6749.The following providers are supported.