Troubleshooting MQRC 2035 Authorization Error in Intercom Integration | Community
Skip to main content

Hello everyone.

I'm experiencing an MQRC 2035 (Authorization) error when integrating Intercom with our messaging queue system. The setup involves deploying an application with MQ Client Connection Properties, specifying all necessary details.

While trying to resolve the issue, I reached out to RabbitMQ support to ensure our configurations were correct. Despite Intercom running as the root user and the queue manager using default mqm users, the connection still fails. The error message indicates a failure to connect to the queue manager on the specified hostname and port.

Has anyone encountered this issue while integrating Intercom with a messaging queue? What steps did you take to resolve it?

Any insights or suggestions would be greatly appreciated.

Hey! This is an MQ permissions/connection issue, not specific to Intercom.

I’d suggest checking with your MQ admin or RabbitMQ support if they can see the request it sends on the backend and the response to it, to help you, make sure the user has proper authorities and that channel authentication allows the connection.

Intercom is just the client; it appears that the problem lies with the queue setup itself!

The MQRC 2035 Authorization error usually means the connecting user lacks proper permissions. A few things to check:

Ensure the MQ Client user is correctly mapped to the queue manager user.

Review channel authentication (CHLAUTH) rules—these can block connections even for root.

Verify the user has the right permissions on the queues (setmqaut can help).

Double-check hostname, port, channel, and SSL/TLS settings.

Many teams resolve this by creating a dedicated user with explicit queue permissions instead of relying on root or mqm defaults.

Reply


Terms & Conditions