Test credentials for Discovery and Orchestration

You can test your credentials directly from the Credentials record without launching a Discovery or an Orchestration workflow.

Before you begin

Role required: discovery_admin, admin

About this task

You can submit a credential record first and then test it later, or test the credential immediately before saving it. The exceptions are Amazon Web Services (AWS) credentials, which must be saved prior to testing.
Note: Credentials are encrypted at all times during the test.

Credential testing is supported for these credential types:

  • SSH (including private keys)
  • Windows
  • SNMP (including v3)
  • VMware
  • JDBC
  • JMS
  • AWS

This procedure assumes you are testing the credential before submitting it.

Procedure

  1. Navigate to Discovery > Credentials and click New.
  2. Select the type of credentials to create.
  3. Enter your credentials in the record fields.
  4. Under Related Links, click Test credential.
    The test runs immediately for AWS credentials. There are no test fields to complete for these credentials, because they do not use a MID Server and are based on the account specified in the credentials record.
  5. For all other credential types, complete the fields in the Test Credential dialog box.
    Figure 1. Test credentials dialog box
    Test credentials dialog box
    Table 1. Credential test fields
    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.
    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. 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.