WMQ On Unix Pattern: Change User Step Not Executing<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: Lato, sans-serif; max-width: 100%; color: #333; line-height: 1.7; } .kb-wrapper h2 { font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 8px; margin: 24px 0 12px 0; } .kb-wrapper p, .kb-wrapper li { font-size: 12pt; margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 12px 0 12px 20px; padding: 0; } .kb-wrapper li { margin-bottom: 8px; } .kb-wrapper .step-list { counter-reset: step-counter; list-style: none; margin: 12px 0; padding: 0; } .kb-wrapper .step-list li { counter-increment: step-counter; margin-bottom: 12px; margin-left: 50px; position: relative; } .kb-wrapper .step-list li:before { content: counter(step-counter); position: absolute; left: -50px; width: 36px; height: 36px; background-color: #032D42; color: #63DF4E; border-radius: 50%; display: flex; align-items: center; justify-content: center; font-weight: 900; font-size: 14pt; } .kb-wrapper .callout { border-left: 4px solid #52B8FF; background-color: #e6f4ff; padding: 12px 12px 12px 16px; margin: 16px 0; } .kb-wrapper .callout.warning { border-left-color: #e6a817; background-color: #fff4e0; } .kb-wrapper code { background-color: #e6f0f5; color: #032D42; padding: 2px 6px; border: 1px solid #b8cfd8; border-radius: 3px; font-family: 'Courier New', monospace; font-size: 11pt; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper .disclaimer { font-size: 10pt; font-style: italic; color: #666; margin: 8px 0; } Issue WMQ On Unix discovery pattern fails at Step 9.1 (Change User), causing Step 9.2 (Get MQ Status Info) to fail with error AMQ8135E: Not authorized. This issue has been identified as PRB2041387. Subscribe to this problem record to receive notifications when a permanent fix is released. Symptoms Step 9.1 completes in 0 ms with SUCCESS status, but user context does not changeStep 9.2 fails with AMQ8135E: Not authorizedQueue manager status and configuration data are not retrieved Facts Affected: WMQ On Unix pattern (MQ Enrich Attributes Library), Step 9.1 - Change User The Change User step attempts an interactive su command, which is incompatible with non-interactive MID Server SSH sessions. Release All Versions Cause The interactive su command used in Step 9.1 is incompatible with non-interactive MID Server SSH sessions. The command presents an interactive password prompt that the MID Server cannot respond to, causing a false SUCCESS status while the user context remains unchanged. Subsequent MQ commands execute under the original SSH user, which lacks IBM MQ administrative privileges. Resolution ServiceNow has updated the WMQ On Unix pattern to remove the problematic interactive user-switch logic. MQ commands now execute directly with the SSH discovery user, which must be a member of the mqm group on the target host. To apply the fix: Download and import the update set provided by ServiceNow support sys_update_set_cdbf31db87a9031016fe62073cbb351e.xmlVerify the SSH discovery credential user has mqm group membership on the target MQ hostRe-run WMQ discovery Note: Applicative credentials of type cmdb_ci_appl_ibm_wmq are no longer required for Unix/Linux MQ discovery. Permanent Fix: This issue is being tracked as PRB2041387. Subscribe to this problem record to be notified when a permanent fix is released in an upcoming product version. Related Links Run a Discovery Discovery Credentials Service Mapping Commands Requiring a Privileged User