Online Help | Network Inventory

Audit Credentials window

Introduced in 8.5

Use the Audit Credentials window to add or modify a set of credentials for auditing computers or other devices using the Direct Network Scan. This article describes controls available in this window.

These types of credentials exist: Windows, Linux and Mac, ESXi/vSphere/Citrix, Google, SNMP.

  • Windows

    Windows credentials are used to audit Windows computers. The audit account that you define must be a member of the local Administrators group on each Windows client computer, either directly or through the membership in a Windows domain group.

    We recommend that you use a domain administrator's account. You can also specify a local account as long as this account exists on every computer you want audited.

    ClosedRead about the Windows Audit Credentials window:

    • Name - the name for the credential record. The name appears in the grid of available audit credentials that you choose in the Select Audit Credentials window.

    • User Name - the account name.

    • Password - the password.

    • Domain - the domain name for a domain account.

      If you want to use a local account, keep the default <Local Computer> value. Note that this local account must exist on every computer you want audited.

    • Test Login - click this button to verify that the account can log in to the specified domain.

  • Linux and Mac

    Linux and Mac credentials are used to audit Linux and macOS computers . Credentials must allow logging on to these computers.

    We recommend that you provide credentials for an account with root rights, i.e. the root account or the account that can run the dmidecode command with administrative rights. Otherwise, Network Inventory will not be able to collect SMBIOS hardware informational on Linux computers. Collecting the list of services (daemons) on macOS computers also requires root rights. If you need this information, you should also use the root account or configure the launchctl command to run with elevated (root) privileges under a non-root account.

    For connecting to Linux and Mac computers via SSH, Network Inventory utilizes Plink-a command-line network connection tool which is a part of the PuTTY product, distributed under the free MIT license. Plink is included in the Network Inventory installation package; the executable file name is plink.exe. For more information on PuTTY and Plink, see the following website: https://www.chiark.greenend.org.uk/~sgtatham/putty/.

    ClosedRead about the Linux and Mac Audit Credentials window:

    • Name - the name for the credential record. The name appears in the grid of available audit credentials that you choose in the Select Audit Credentials window.

    • Protocol - this field is read-only. Connection to the Linux and Mac computers is always established through the Secure Shell protocol (SSH).

    • Port - by default, Network Inventory accesses client Linux and Mac computers over the standard TCP port 22. If you want to specify a non-standard TCP port that the SSH server running on client computers listens on, enter its number.

    • Username - the account name.

    • Password - the account password.

    • Private Key - this field is read-only. It displays information about the private key file uploaded to the database.

    • Browse - click this button to choose your private key file.

    • Clear - clears the Private Key field.

    • Use custom command line parameters - select this check box if you want to manually specify Plink command line parameters.

    • Parameters - this field becomes available when you select the check box above. It contains parameters of the Plink command line. The default command line parameters may look like this:

      -P "$PORT" -l "$USER_NAME" -pw "$PASSWORD" "$HOST"

      In this example, "$PORT", "$USER_NAME", "$PASSWORD", and "$HOST" are placeholders for command line parameter values, corresponding to the dialog box fields. For more information on placeholders, see below.

      The default parameters may include port (-p), user name (-l), password (-pw) or private key (-i). You can edit the command line as needed. For a complete list of Plink parameters, please refer to http://the.earth.li/~sgtatham/putty/0.58/htmldoc/Chapter7.html#plink.

      You can configure a custom command line in two ways:

      • You can specify parameter values directly in the command line (e.g. -p "22"). In this case, you are not required to fill out the dialog box fields. However some parameters, such as private key and host, cannot be specified in this way.

      • You can use placeholders instead of specific values (e.g. -p "$PORT"). The actual values for placeholders are taken from the corresponding dialog box fields, which you must fill out. Note that the values for the private key and host must always be passed as placeholders. The value for the $HOST placeholder is determined automatically for each audited computer, hence there is no corresponding dialog box field.

      NOTE: Currently, Network Inventory does not support SSH authentication via the Pageant authentication agent. As a possible solution, you can specify your private key file directly in the audit credentials.

    • Insert Placeholder - inserts a placeholder into the Parameters field.

  • ESXi/vSphere/Citrix

    ESXi/vSphere/Citrix credentials are used to audit ESXi/vSphere and Citrix hypervisors. Credentials must allow logging on to these computers. We recommend that you use an account with administrative privilege. For Citrix hypervisors, audit credentials must allow logging to the computers using the SSH protocol.

    ClosedRead about the ESXi/vSphere/Citrix Audit Credentials window:

    • Name - the name for the credential record. The name appears in the grid of available audit credentials that you choose in the Select Audit Credentials window.

    • Protocol - this field is read-only. Connection to the Linux and Mac computers is always established through the Secure Shell protocol (SSH).

      NOTE: Network Inventory establishes connection to Linux and Mac computers using the Secure Shell protocol (SSH) over a TCP port. Therefore, it is required that the SSH server is running on each client computer and listening on a dedicated TCP port.

  • Google

    Google credentials ate used to collect audit data on Google Chromebooks. Google credentials must allow access to the inventory information about Chromebooks enrolled in the domain.

    ClosedRead about the Google Audit Credentials window:

    • Name - the name for the credential record. The name appears in the grid of available audit credentials that you choose in the Select Audit Credentials window.

    • Client ID - the Google developer API Client ID.

    • Client Secret - the Google developer API Client Secret.

    • NOTE: You can load both the Client ID and the Client Secret parameters using the Load button. For details, see Google Directory Audit and Directory API: Getting Started.

    • Domain - the name of domain, if you want to specify a domain user name.

    • Authorize - click this button to start the authorization process. In a browser window, sign in with the Google Account to your domain and configure client permissions by clicking the Allow button. When the authorization is approved, the credentials will be saved automatically.

  • SNMP

    SNMP credentials are used to collect inventory data about networked printers, scanners, hubs, routers, and other devices. Network Inventory detects and identifies those network devices via SNMP.

    ClosedRead about the SNMP Audit Credentials window:

    • Name - the name for the credential record. The name appears in the grid of available audit credentials that you choose in the Select Audit Credentials window.

    • Under Version v1/v2c, specify the following information for community-based SNMPv1 or SNMPv2c:

      • Community - the SNMP community.

        NOTE: Most SNMP v1 and v2c devices are shipped with the community string set to "public". It is standard practice for system administrators to change the community strings so that unauthorized users cannot access information about the internal network.

    • Under Version v3, specify the following information for user-based SNMPv3:

      • User Name - the SNMP user name.

      • Security Level - the SNMP security level:

        • No Authentication, No Privacy - uses a user name for authentication and transmits credentials in clear text.

        • Authentication, No Privacy - provides packet authentication and message integrity, but no encryption. Select the authentication algorithm (MD5 or SHA) in the Protocol list and type in the pass phrase.

        • Authentication, Privacy - provides the maximal security by combining authentication, message integrity, and encryption. Under Authentication, select the authentication algorithm (MD5 or SHA) and type in the pass phrase. Under Privacy, select the encryption algorithm (DES or AES) and type in the pass phrase.

Related Information:

Managing Audit Credentials