--- 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 --- # Create and test your credentials # Create and test your credentials {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Create and test the credentials that Discovery, Service Mapping, Cloud Management, and Orchestration require to access hardware and software in your network.{#t_CreateCredential__ph_CreateCredentials} ## Vorbereitungen Role required: admin Review your security policy and options with your organization's security team. ## Warum und wann dieser Vorgang ausgeführt wird This task contains general procedures for creating credentials. Refer to the documentation for your credential type for details on specific fields and requirements. |-|-|-| | [Applicative credentials](https://servicenow-prod.fluidtopics.net/LjOX6cikzrPTk6DK0Lsr5Q "Some applications require credentials in addition to the credentials the that host machine requires. Credentials required to access these applications are referred to as applicative credentials.") | [Basic authentication credentials](https://servicenow-prod.fluidtopics.net/V8ueJqgeYRL1wyvfgqyFBw "The basic authentication credential type manages access to store basic authentication credentials.") | [Chef server credentials](https://servicenow-prod.fluidtopics.net/m8ncV0flkaDTvMnSlfWQEw "Chef server credentials access chef integrations with the instance.") | | [CIM credentials](https://servicenow-prod.fluidtopics.net/YbOYrD5YBFF~zP_Iof9KVw#r_CIMCredentialsForm "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.") | [Cloud credentials](https://servicenow-prod.fluidtopics.net/e4txscD2kAqHeV_wywwswQ "Cloud credential types manage access to cloud-based applications, including Amazon Web Services and the Microsoft Azure cloud.") | [Container image repository credentials](https://servicenow-prod.fluidtopics.net/KBL6eZKmuiTzZIsQuCY6Ng "The container image repository credentials manage access to private repositories for container image scanning. This credential type is available for Discovery.") | | [Infoblox credentials](https://servicenow-prod.fluidtopics.net/AA6T0l_4vb8AvIvVqTITAQ "Infoblox credentials are required to set up IP pools (IPAM) in the Cloud Management application.") | [JDBC credentials](https://servicenow-prod.fluidtopics.net/2jPJny4ZZoLvA~JDe6q_tQ "The JDBC credential type manages access to a Java Database Connectivity (JDBC) connection. This credential type is available for Discovery and Orchestration.") | [JMS credentials](https://servicenow-prod.fluidtopics.net/wbu7lhnYGtdiWZcy4YkXjw "The JMS credentials type manages access to a Java Message Service (JMS). This credential type is available for Discovery and Orchestration.") | | [OAuth 2.0 credentials](https://servicenow-prod.fluidtopics.net/TfU7VSlomRViHT7l6Zvryg "OAuth 2.0 credentials enable ServiceNow to obtain access to user accounts on an HTTP service.") | [SAP credentials](https://servicenow-prod.fluidtopics.net/M9R0k6eDmLQeN5htT9jsjA "The SAP credential type manages access to SAP JCo systems. This credential type is available for Discovery and Orchestration.") | [SNMP credentials](https://servicenow-prod.fluidtopics.net/DarmBQMv~dK8hToGw1AHQA#c_SNMPCredentials "Discovery explores many kinds of devices (switches, routers, printers, and so on) using the SNMP protocol. Credentials for SNMP don’t include a user name, just a password, called the community string.") | | [SSH credentials](https://servicenow-prod.fluidtopics.net/jjoq2so7dgrp70wj6qHfGA "Discovery, Orchestration, and Integration Hub explore UNIX and Linux devices by using SSH credentials to execute commands over Secure Shell (SSH). SSH commands must run with root privileges, either with root credentials or through the use of sudo. SSH private key credentials provide additional security.") | [VMware credentials](https://servicenow-prod.fluidtopics.net/hlUMEN1RSvMBxKpmDF_XpA "The VMware credentials type manages access to vCenter credentials.") | [Windows credentials](https://servicenow-prod.fluidtopics.net/aUQ45WtPlDznfpJCw6Yyfg#r_WindowsCredentialsForm "Windows credentials provide access to Windows computers. This credential type is available for Discovery and Orchestration.") | [Tabelle : 1. Supported credential types] {#t_CreateCredential__table_sbq_p4k_1cb} Hinweis: To improve security, limit the scope of credentials to a specific MID Server or schedule to avoid unnecessary credentials. ## Prozedur 1. Navigate to one of these modules: * DiscoveryCredentials * Service MappingCredentials * OrchestrationCredentials {#t_CreateCredential__ul_f52_hbb_1w} 2. Click New. 3. On the Credentials page, click a link for the credential type and complete the form. Refer to the documentation for the credential type you selected for details. You can submit a credential record first and then test it later, or test the credential immediately before saving it. Credential testing is supported for these credential types: * SSH private keys * Windows * SNMP v3 * VMware * JDBC * JMS {#t_CreateCredential__ul_at4_3jn_25} 4. Under Related Links, click Test credential. Hinweis: Credentials are encrypted at all times during the test. 5. Complete the fields in the Test Credential dialog box. Abbildung : 1. Test credentials dialog box {#t_CreateCredential__table_uxn_qln_25__entry__3} | Field | Description | Credential type | |-|-|-| | Target | Target host on which these credentials are run. This value must be an IP address for all credential types except VMware, which can be the host URL. You can not target any MID servers. Hinweis: For JMS, this is the provider URL. The information in this URL tells JNDI how to find and access the JMS Provider. An example value for connecting to ActiveMQ V5.1, is tcp://ipAddressOrHostName:61616. | All | | Port | Port on the target to use for this test. The system pre-populates this field with the default port for the selected credential type. | All | | MID Server | MID Server to use for this test. You must use a Windows MID Server to test Windows credentials. Only Up and Validated MID Servers are available. | All | | DB Type | Type of database on which to test these credentials. | JDBC | | DB Name | Name of the database on which to test these credentials. | JDBC | | Initial Context Factory | Name of the JNDI class that is used to create the InitialContext. Using this Initial Context Factory, various JMS objects, such as JMS Connection, are created. For example, to connect to ActiveMQ V5.10, (JMS Provider), the value in this field would be org.apache.activemq.jndi.ActiveMQInitialContextFactory | JMS | [Tabelle : 2. Credential test fields] {#t_CreateCredential__table_uxn_qln_25} 6. Click OK to begin the test. An indicator appears, showing that the system is attempting to contact the target using the credentials you have provided. When the instance connects to the target it displays a success message. If the instance encounters a problem with the test inputs you have provided, it displays the appropriate error message. The following are some common error messages. * Incorrect target or port number: Abbildung : 2. TCP connection failure * Incorrect user name or password: Abbildung : 3. Authentication failure * Incorrect MID Server for Windows credentials: Abbildung : 4. MID Server error {#t_CreateCredential__ul_ob1_xl1_f5} 7. Click Retry to open the test Credential dialog box and correct the input error. 8. When your credentials test is successful, click Submit to save the record. Wichtig: Testing credentials does not ensure that the credentials have the necessary privileges required for the intended Discovery or Orchestration workflow tasks.