# Scan domain that requires login

{% hint style="success" %}
**Access Type**: Compliance Report - Editor

**Premium Feature**: Advanced Compliance Monitoring or XL Scan
{% endhint %}

Utilizing the Advanced Compliance Monitoring or XL Scan feature, your organization can generate compliance reports for domains that require a login. In this article, we will cover how to configure a compliance report scan on a domain for the following login forms:

| [Single-step (combined) login](#single-step-combined-login) | All credentials are collected and submitted in one interaction *(i.e. the username, password, and submit button are on the same page)*                 |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Multi-step login](#multi-step-login)                       | User identity is established before prompting for authentication secrets *(e.g. User submits user name first and inputs password in a secondary step)* |

{% hint style="info" %}
Didomi currently does not support two-factor authentication (2FA) scanning.
{% endhint %}

To start, click **Advanced Compliance Monitoring** or **Compliance Monitoring** on the left-hand panel and either [add a new domain](/compliance-report/compliance-report-domains/add-domain-to-compliance-report-classic.md) or [edit an existing domain](/compliance-report/compliance-report-domains/edit-compliance-report-domain.md). 

<figure><img src="/files/QY7isB0LRMGxXEBRrST7" alt="" width="563"><figcaption></figcaption></figure>

***

### Single-step (combined) login

If the login form used by the domain is a traditional login form where the credentials are collected and submitted in a single interaction then your organization can utilize the **Scan logged in environment** feature. This feature will log you in for all scenarios included in the scan and provide password encryption by Didomi.&#x20;

Expand the **Scan logged in environment** accordion on the subsequent page and enable the checkbox for **Scan logged environment**.&#x20;

<figure><img src="/files/TsUoUD0Nf1Iy6YG3ysCp" alt="" width="563"><figcaption></figcaption></figure>

Your organization will be prompted to input required credentials and/or optional CSS selectors to aid the Didomi bot in accessing the domain and performing its scan. Click the tabs below to learn more.

{% tabs %}
{% tab title="Required credentials" %}
In order to scan an environment that requires end-user login, your organization must provide the following information when configuring the compliance report for the domain:

<table><thead><tr><th width="206">Field</th><th>Description</th></tr></thead><tbody><tr><td>Login page URL</td><td>Login form where URL is present</td></tr><tr><td>Username</td><td>Username that will be used by the Didomi bot to log into your website</td></tr><tr><td>Password</td><td>Password associated with the username that will be used by the Didomi bot to log into your website<br><br><mark style="background-color:$warning;"><strong>Note</strong>: The password is encrypted by Didomi to avoid causing any security breaches.</mark></td></tr></tbody></table>

<figure><img src="/files/LSbiOL5ivVjpBoUL27PJ" alt="" width="563"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="CSS selectors (optional)" %}
The Didomi bot will automatically attempt to insert the username and password in the appropriate fields, and select the submission button when accessing your website. Your organization can directly configure the Didomi bot's actions when inserting and selecting the submission button by giving it the CSS selectors of the appropriate fields/buttons.

To collect the CSS selector values for the username, password, and submission button field:

1. Navigate to your login page URL
2. Right-click the desired element on the page where the Didomi bot should insert the required text/click the button
3. Select **Inspect** from the subsequent menu

<figure><img src="/files/EZoaahE2UbMpy6WM0Dkf" alt="" width="375"><figcaption></figcaption></figure>

The element should be highlighted in the Inspector. Right-click the highlighted item in the Inspector and select **Copy > Copy selector** (or **CSS Selector** depending on browser).

<figure><img src="/files/3cCPRXdKXqhQ3RPoV8CT" alt="" width="563"><figcaption></figcaption></figure>

Navigate to your compliance report configuration and add the copied value to the appropriate field for the element.

<figure><img src="/files/2tGmtRbNWUvinS8gXl5O" alt="" width="563"><figcaption></figcaption></figure>

Repeat as necessary for the remaining fields
{% endtab %}
{% endtabs %}

### Multi-step login

If the login form used by the domain is a multi-step form where end-users provide credentials in separate steps (such as the identifier-first login used by Google or Microsoft) then your organization will need to manually customize each scenario in the compliance report scan.&#x20;

* Retrieve CSS selectors
* Configure Bot scenarios with multi-step login

{% hint style="warning" %}
**Note**: When configuring a scan for a domain that utilizes a multi-step login, do not enable the **Scan logged in environment** feature.

Additionally, please be aware that Didomi does not provide password encryption Didomi-side for multi-step login forms.
{% endhint %}

#### Retrieve CSS selectors

CSS selector values will instruct the Didomi bot where to click (or insert text) in the login form. To collect the CSS selector values:

1. Navigate to the login form
2. Right-click the desired element of where the Didomi bot should click (or insert text)
3. Select **Inspect** from the subsequent menu

<figure><img src="/files/KWOeBLzC0tpASb884lvT" alt="" width="375"><figcaption></figcaption></figure>

The element should be highlighted in the Inspector. Right-click the highlighted item in the Inspector and select **Copy > Copy selector** (or **CSS Selector** depending on browser).

<figure><img src="/files/AsS9FYjNnqJ8yXbaIQdV" alt="" width="563"><figcaption></figcaption></figure>

Repeat the above steps to retrieve all CSS selectors the Didomi bot will need to interact with to successfully log into the website.

#### Configure Bot scenarios with multi-step login

With the CSS selectors copied, expand the accordion for a scenario and utilize the **Add an instruction** tools to select the first step in the login flow.

<figure><img src="/files/pzMjX5UUkOyCZHbiRZVG" alt="" width="563"><figcaption></figcaption></figure>

Depending on the instruction selected, your organization will need to input the following:

| Instruction | Required fields                                                                                                                   |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Click       | <ul><li>CSS selector </li></ul>                                                                                                   |
| Fill in     | <ul><li>Text to input into the field for your login form</li><li>CSS selector of the field where a user inputs the text</li></ul> |

<figure><img src="/files/6cwGP2jXn4XHrUSGK2cB" alt="" width="563"><figcaption></figcaption></figure>

Repeat as necessary to reproduce the sequential steps needed to successfully login. When finished, use the provided arrows to ensure that the login steps precede any actions performed for the consent notice.

<figure><img src="/files/MQBEQcg12GuuhK74eqTc" alt="" width="563"><figcaption></figcaption></figure>

Click **Save and Run** when finished.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.didomi.io/advanced-compliance-monitoring-acm/compliance-report-acm/scan-domain-that-requires-login.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.