JDBC credentials

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 in ServiceNow manages access to Java Database Connectivity (JDBC) connections and is used primarily in Discovery and Orchestration processes. It allows you to securely store and manage database credentials necessary for connecting to and interacting with JDBC-enabled data sources.

    Show full answer Show less

    Key Features

    • Name: Assign a unique, descriptive name to identify each JDBC credential.
    • Active: Enable or disable credentials to control their availability for use.
    • User name and Password: Enter credentials for database access, ensuring no leading or trailing spaces. For CIM discovery, the user requires the admin role.
    • Credential ID: Used when leveraging external credential stores, representing the unique key for the credential stored in a JAR file on the MID Server. This field replaces user name and password when external storage is enabled.
    • Credential alias: Allows assigning specific credentials to individual activities within Orchestration workflows or different occurrences of the same activity, supporting flexibility in credential use.
    • External credential store: Option to use an external system for storing credentials, currently supporting CyberArk when the External Credential Storage plugin is activated.
    • Applies to and MID servers: Define whether credentials are available to all MID servers or specific ones, controlling which MID servers can access the credentials. Note that specifying specific MID servers affects visibility but not selection during orchestration activities.
    • Order: Determines the sequence in which Discovery attempts credentials to log on to devices, helping manage login attempts and avoid lockouts.
    • Windows MID Server Service Account: Marks the credential as representing the MID Server service account when active.

    Practical Application for ServiceNow Customers

    By configuring JDBC credentials correctly, customers can enable Discovery and Orchestration to securely access databases via JDBC connections. Using features like credential aliasing and external credential storage improves security and flexibility when managing multiple credentials across different workflows and MID servers. Setting credential order optimizes login attempts, reducing the risk of lockouts during Discovery. Activating the Windows MID Server Service Account credential ensures proper MID Server authentication.

    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.