feat(ibmmq): clarify required persmissions #17178
Conversation
|
Hi @paologallinaharbur 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@paologallinaharbur - thanks for this! It's a little unclear to me which permissions need to be added. It lists the capabilities but not what permissions need to be granted. Am I missing something? |
homelessbirds
added
content
|
No, I think it is just my "English" having some issues 😄 I though that "being able to access a QM" or "being able to access a specific channel" was considered a |
| - connect to the queue manager having `DISPLAY` and `INQUIRY` enabled. | ||
| - access the channel specified in the integration config (by default `SYSTEM.DEF.SVRCONN`) | ||
| - operate priviledge commands on queues `SYSTEM.DEFAULT.MODEL.QUEUE` and `SYSTEM.ADMIN.COMMAND.QUEUE` having the `Display` permission. | ||
| - access with `Display` and `Subscribe` for the topics `SYSTEM.ADMIN.TOPIC` and `SYSTEM.BROKER.ADMIN.STREAM` |
There was a problem hiding this comment.
these are the permissions required, however some additional one are needed depending on their specific setup
...ocs/infrastructure/host-integrations/host-integrations-list/ibmmq-monitoring-integration.mdx
Outdated
Show resolved
Hide resolved
…tions-list/ibmmq-monitoring-integration.mdx
Updating ibmmq permissions specifications https://new-relic.atlassian.net/browse/NR-259871, https://new-relic.atlassian.net/browse/NR-262491