---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Credentials required for host discovery

# Credentials required for host discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

There are credentials and permissions that Service Mapping requires for discovering hosts.
Prior to discovering applications, Service Mapping accesses hosts that applications run on and discovers them. Make sure that you provide all necessary credentials to allow host discovery.

The ServiceNow AI Platform provides a centralized way of configuring credentials for Discovery, Service Mapping, and other applications. It allows you to configure credentials for hosts and applications only once. If you have already configured host-related credentials for another application, you do not need to do it again for Service Mapping.{#r_Credentials4HostDiscovery__conref_host_related_credentials}

## Credentials required for discovery of hosts running on UNIX or Linux

Discovery, Orchestration, and Integration Hub explore UNIX and Linux devices by using SSH credentials to execute commands over Secure Shell (SSH).  
To provide sufficient permissions, configure one of the following UNIX and Linux credentials:

* Non-root user and password and using the 'sudo' utility to run selected commands as root
* Root user and password
{#r_Credentials4HostDiscovery__ul_zss_prq_bv}

For information on commands requiring sudo-level rights, see [Service Mapping commands requiring a privileged user](https://servicenow-prod.fluidtopics.net/KmX~uDsV3RoqnUbrW~2SFA "Service Mapping uses commands requiring elevated rights to discover and map Unix-based hosts in your organization. In addition to configuring necessary credentials, configure servers in your organization to allow Service Mapping to run these commands with elevated rights.") and [Commands that require root privileges for Discovery and Orchestration](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).  
To access Unix-based hosts with non-root credentials, provide the read access to the following files and directories:

* /etc/\*release
* /etc/bashrc
* /etc/profile
* /proc/cpuinfo
* /proc/vmware/sched/ncpus
* /var/log/dmesg
* APD directory
{#r_Credentials4HostDiscovery__ul_mq4_jkn_dw}

## Credentials required for discovery of hosts running on Windows servers

To provide sufficient permissions, configure one of the following Windows credentials:

* A domain user with local administrator access on the target Windows hosts.
* A domain administrator.  
  Note:  
  You may need domain administrator credentials only in some cases. For example, when discovering domain controllers.

{#r_Credentials4HostDiscovery__ul_stl_w2s_x4}

Configure MID Server to use [Windows credentials](https://www.servicenow.com/docs/access?context=r_WindowsCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).

(Optional) For discovering using the WinRM protocol, see [Configure WinRM trusted hosts on MID Server](https://www.servicenow.com/docs/access?context=enable-winRM-MID-servers&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

## Resolving credential-related issues {#r_Credentials4HostDiscovery__section_nnp_2vh_hcc}

If there are discovery issues caused by incorrectly configured or missing credentials, resolve them as explained in the KB article: [Credentials \& Permissions troubleshooting on Discovery, Service Mapping, Orchestration](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657528)