Create and test the credentials that Discovery, Service Mapping, Cloud Management, and Orchestration require to access hardware and software in your network.

Before you begin

Role required: admin

Review your security policy and options with your organization's security team.

About this task

This task contains general procedures for creating credentials. Refer to the documentation for your credential type for details on specific fields and requirements.
Table 1. Supported credential types
Applicative credentials Basic authentication credentials Chef server credentials
CIM credentials Cloud credentials Container image repository credentials
Infoblox credentials JDBC credentials JMS credentials
OAuth 2.0 credentials SAP credentials SNMP credentials
SSH credentials VMware credentials Windows credentials
Note: To improve security, limit the scope of credentials to a specific MID Server or schedule to avoid unnecessary credentials.

Procedure

  1. Navigate to one of these modules:
    • Discovery > Credentials
    • Service Mapping > Credentials
    • Orchestration > Credentials
  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
  4. Under Related Links, click Test credential.
    Note: Credentials are encrypted at all times during the test.
  5. Complete the fields in the Test Credential dialog box.
    Figure 1. Test credentials dialog box
    Test credentials dialog box
    Table 2. Credential test fields
    FieldDescriptionCredential 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.
    Note: 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
  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:
      Figure 2. TCP connection failure
      TCP connection failure
    • Incorrect user name or password:
      Figure 3. Authentication failure
      Authentication failure
    • Incorrect MID Server for Windows credentials:
      Figure 4. MID Server error
      MID Server error
  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.
    Important: Testing credentials does not ensure that the credentials have the necessary privileges required for the intended Discovery or Orchestration workflow tasks.