JMS credentials
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- External Credential Storage
The JMS credentials type manages access to a Java Message Service (JMS). This credential type is available for Discovery and Orchestration.
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. |