|  |
| Field | Description |
|---|---|
| Authentication Type | - **Basic** Username and password based authentication. - **Mutual** Client certificate based authentication. See [MID Server unified key store]() for more information on mutual authentication. **Note:** Selecting mutual authentication disables the MID Server username and password fields. The disabled fields are not written to **config.xml**. |
| ServiceNow instance URL | Enter the full URL of your instance, for example: `https://mycompanyinstace.service-now.com` |
| ServiceNow MID Server username | Enter the name of the [MID Server user](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/t_SetupMIDServerRole.md) that you already created. The MID Server user must have the mid\_server role. |
| ServiceNow MID Server password | Enter the password for the user in the **ServiceNow MID Server username**. |
| Certificate Revocation | This check box is selected by default to enable certificate revocation policies to improve security. For more information on certificate revocation, see [MID Server certificate check policies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/mid-security-checks.md). When testing a connection with certificate revocation enabled, the installer checks if OCSP port 80 is open and the entrust page is accessible. If the connection test fails due to the certificate revocation check, the error must either be corrected and re-tested or the certificate revocation check must be disabled. The certificate revocation check is not required for successful installation. |
| Use proxy | Select this check box if your MID Server communicates through a proxy to connect to the instance.**Note:** Your proxy server must use Basic Authentication for the MID server to connect to the instance. The MID Server can bypass proxy servers whose DNS/IP address is listed in the configuration parameter **mid.cloud.discovery.proxy.exclusion.list**. See [MID Server property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/r_MIDServerProperties.md) for more information. |
| Proxy Host | Enter the proxy server host name or IP address. Do not include the protocol in the host name. For example, enter `proxyserver.domain.com`, not `https://proxyserver.domain.com`. |
| Proxy Port | Enter the port through which the proxy server communicates. If you leave this field blank, it should use the proxy server's default port number. |
| Proxy Username | Enter the username for the proxy server. |
| Proxy Password | Enter the password for the user name. |
| Field | Description |
|---|---|
| MID Server name | Enter a MID Server name.**Warning:** MID Server names cannot begin with **mid.server**. |
| Service Account Name | Username of the service account that will be used to run the MID Server service. For information on creating service accounts, see [Create a Windows service account with "Log on as Service" \[KB0867669\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867669). The Service Account Name field is an editable drop-down menu. Either select a value from the drop-down or type a new value in the text field. Only the accounts with **log on as service** policy are displayed in the drop-down. Group Managed Service Accounts \(gMSA\) that inherit the **log on as service** policy from their groups are not displayed in the drop-down. However, you can install the MID Server service using those accounts by manually entering the service account name in the editable drop-down. The name can follow three formats. 1. If the service account is local to the computer, you can give just the name. Example: My\_Local\_Service\_Account 2. If the service account is local to the computer, you can provide "." as the domain name for the account. Example: .\\My\_Local\_Service\_Account 3. Any account can follow the format \{domain\}\\\{username\}. Example: MY-COMPUTER-DOMAIN\\My\_Domain\_Service\_Account Add a new local service account by selecting the **+** button. This button opens the **Configure New Local User** window, which has three fields. - **Service Account Name:** Enter the name of the new service account. - **Service Account Password:** Enter the password of the new service account. - **Re-enter Password:** Confirm the password of the new service account. When a group Managed Service Account \(gMSA\) user is selected, the password field is removed because passwords for gMSA users are managed by the Active Directory. **Note:** The provided service account credentials must meet the following requirements in addition to being a valid account. - The user cannot be a local system or an administrator level account \(local admin, domain admin, etc.\) - The service account provided has the **log on as service** right, which is required for an account to be used as the **log on user** for a service. |
| Service Account Password | Password of the service account that will be used to run the MID Server service. |
| Set Service Name Manually | Select this check box if you want to manual set the service name and display name for your MID Server. Note: Your proxy server must use Basic Authentication for the MID server to connect to the instance. |
| MID Service wrapper name | Modify this field if necessary. It is populated automatically by prefixing `snc_mid_` to the MID Server name. In most cases, you do not need to modify this. |
| MID Server wrapper display name | Modify this field if necessary. It is populated automatically by prefixing `ServiceNow MID Server_` to the MID Server name. In most cases, you do not need to modify this. |