JMS 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 JMS credentials

    The JMS credentials type in ServiceNow manages access to Java Message Service (JMS) environments and is used primarily for Discovery and Orchestration processes. It enables secure authentication by storing necessary user information and integrating with external credential storage systems when needed.

    Show full answer Show less

    Key Features

    • Name and Activation: Assign unique, descriptive names to each credential and enable or disable them as needed for use.
    • User Name and Password: Specify the user name and password for authentication. The platform warns against leading or trailing spaces. For CIM discovery, the user requires the admin role.
    • Credential ID and External Credential Store: When using an external credential storage system (such as CyberArk, supported via the External Credential Storage plugin), the Credential ID replaces the user name and password fields. This ID is limited to 40 characters.
    • Credential Alias: Allows workflow creators to assign different credentials to specific activities or multiple instances within Orchestration workflows, enabling flexible credential management.
    • CI Type Table Name: For discovering Configuration Items (CIs) outside the default type, specify the target CI table name (e.g., cmdbciapachewebserver) to ensure proper discovery.
    • Applies to and MID Servers: Choose whether the credential applies to all MID Servers or specific ones. Assign credentials to selected MID Servers to control visibility and usage. Note that specifying specific MID Servers affects visibility but not selection, and this option is not supported in Orchestration activities.
    • Order: Define the sequence in which Discovery attempts credentials to log into devices. This is useful for managing multiple credentials and avoiding account lockouts after failed login attempts.
    • Windows MID Server Service Account: When enabled, the credential represents the MID Server’s service account.

    Practical Use for ServiceNow Customers

    ServiceNow customers can leverage JMS credentials to securely authenticate Discovery and Orchestration processes against JMS environments. The ability to integrate with external credential stores like CyberArk enhances security and credential management. Setting credential order optimizes login attempts and prevents lockouts, while credential aliasing provides granular control during workflow execution. Applying credentials specifically to selected MID Servers ensures appropriate access control and credential visibility. Proper configuration of these fields enables efficient and secure JMS resource management within ServiceNow.

    The JMS credentials type manages access to a Java Message Service (JMS). This credential type is available for Discovery and Orchestration.

    These fields are available in the Credentials form for JMS.
    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.