Credentials required for host discovery

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 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.

Credentials required for discovery of hosts running on UNIX/Linux:

Discovery and Orchestration explore UNIX and Linux devices by using commands executed over Secure Shell (SSH), so they need SSH credentials.

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

For information on commands requiring sudo-level rights, see Service Mapping commands requiring a privileged user and UNIX and Linux commands requiring root privileges for Discovery and Orchestration.

To access Unix-based hosts with non-root credentials, make sure you have 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

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.

Configure Windows credentials as described in Domain requirements for Windows credentials.

Configure MID Server to use Windows credentials: