JDBC credentials

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of JDBC Credentials

    The JDBC credential type facilitates access to Java Database Connectivity (JDBC) connections, specifically for Discovery and Orchestration processes in ServiceNow. It allows users to manage and configure credentials essential for database access.

    Show full answer Show less

    Key Features

    • Name: Unique identifier for the credential.
    • Active: Option to enable or disable the credential.
    • User Name: User name for the credential, requiring no leading or trailing spaces; admin role is necessary for CIM discovery.
    • Password: Password associated with the user name.
    • Credential ID: Unique key for external credentials, limited to 40 characters, visible only with external credential store selected.
    • Credential Alias: Assigns individual credentials to specific activities in an Orchestration workflow.
    • External Credential Store: Enables use of an external storage system (e.g., CyberArk) when selected.
    • Applies to: Determines if credentials apply to All MID servers or Specific MID servers.
    • MID Servers: Selection of one or more MID servers that can access the credential, applicable only to Specific MID servers.
    • Order: Establishes the sequence for credential usage during Discovery logins; lower numbers are prioritized.
    • Windows MID Server Service Account: Credential can represent the MID Server service account when active.

    Key Outcomes

    By effectively managing JDBC credentials, ServiceNow customers can ensure secure and controlled access to databases during Discovery and Orchestration processes. Proper setup allows for streamlined operations, enhancing security and efficiency in managing database connections. Customers can also prevent login failures and optimize the use of credentials across multiple MID servers.

    The JDBC credential type manages access to a Java Database Connectivity (JDBC) connection. This credential type is available for Discovery and Orchestration.

    These fields are available in the Credentials form for JDBC type credentials.
    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 is only available when the External Credential Storage plugin in activated.
    Note:
    Currently, the only supported external storage system is CyberArk.
    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.
    Note:
    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.