---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# CIM credentials

# CIM credentials {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

The CIM credential type manages access to a CIM server (also referred to as a CIMOM - Common Information Model Object Manager) for information about VMware ESX servers. This credential type is available for Discovery.
These fields are available in the Credentials form for CIM. {#r_CIMCredentialsForm__table_tj2_x3v_2y__entry__2}{#r_CIMCredentialsForm__cred_desc_name}{#r_CIMCredentialsForm__cred_field_active}{#r_CIMCredentialsForm__cred_field_username}

| Field | Description |
|-|-|
| Name | Enter a unique and descriptive name for this credential. |
| Active | Enable or disable these credentials for use. |
| User name | Enter the user name to create in the Credentials table. Avoid leading or trailing spaces in user names. A warning appears if the platform detects leading or trailing spaces in the user name. For CIM discovery, the user must have the admin role. |
| Password | Enter the password. |
| Credential ID | Enter the unique key configured for external credentials in the JAR file uploaded to the MID Server for an external credential system. The Credential ID field has a limit of 40 characters. This field is only visible when the External credential store check box is selected. |
| Credential alias | Allow workflow creators to assign individual credentials to any activity in an Orchestration workflow or assign different credentials to each occurrence of the same activity type in an Orchestration workflow. To use the credential for discovering CIs not belonging to this CI type using Service Mapping and Discovery patterns, enter the table name for the CI type to which the CI belongs, for example cmdb_ci_apache_web_server. |
| External credential store | Select this check box to use an external credential storage system. When you select this option the User name and Password fields are replaced with the Credential ID field. [External credential storage](https://servicenow-prod.fluidtopics.net/AIY__YGd0bmRNXCDShvRPw "An instance can store credentials used by Discovery, Orchestration, and Service Mapping in an external credential repository rather than directly in a ServiceNow credentials record.") is only available when the External Credential Storage plugin in activated. Hinweis: Currently, the only supported external storage system is [CyberArk](https://servicenow-prod.fluidtopics.net/Xpwevyeu6_J73cxiLEgwXA "The MID Server integration with the CyberArk vault enables ServiceNow Orchestration, ServiceNow Discovery, and ServiceNow Service Mapping to run without storing any credentials on the instance."). |
| Applies to | Select whether to apply these credentials to All MID servers in your network, or to one or more Specific MID servers. Specify the MID Servers that should use these credentials in the MID servers field. |
| MID servers | Select one or more MID Servers from the list of available MID Servers. The credentials configured in this record are available to the MID Servers in this list. This field is available only when you select Specific MID servers from the Applies to field. Hinweis: Selecting Specific Specific MID servers doesn't affect mid server selection. It's used only to decide which mid servers should have visibility to the credential. Specific MID servers isn't supported in Orchestration activities. |
| Order | Order (sequence) in which Discovery tries this credential as it attempts to log on to devices. The smaller the number, the higher in the list this credential appears. Establish credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number (or none), the instance tries the credentials in a random order. |
| Windows MID Server Service Account | When active, the defined credential represents the MID Server service account. |
[ ]

{#r_CIMCredentialsForm__table_tj2_x3v_2y}

## Configure NetApp storage devices for CIM credentials {#ariaid-title2}

NetApp storage devices require additional configuration for Discovery to explore them.

### Vorbereitungen

Role required: admin

### Prozedur

1. Install the [SMI-S Provider](https://docs.netapp.com/us-en/smis-provider/task-install-smi-s-agent-on-a-windows-host.html) on the storage device host.  
   See the [Download the NetApp SMI-S Provider software package](https://docs.netapp.com/us-en/smis-provider/task-download-smi-s-provider.html) for instructions and requirements.  
   Hinweis:  
   ServiceNow doesn't maintain the documentation on this site. This document can change without notice.
2. Create a user account and password for the SMI-S agent.
3. Create a credential record for the SMI-S agent credentials.  
   Set the credential type to CIM.