diff --git a/modules/ROOT/pages/_partials/include-permissions-mq.adoc b/modules/ROOT/pages/_partials/include-permissions-mq.adoc index 965651ea..192679f0 100644 --- a/modules/ROOT/pages/_partials/include-permissions-mq.adoc +++ b/modules/ROOT/pages/_partials/include-permissions-mq.adoc @@ -47,15 +47,15 @@ |This permission is deprecated. Assign these permissions instead: * Administer destinations -* Destination subscriber for given environment -* Destination publisher for given environment +* Destination subscriber for a given environment +* Destination publisher for a given environment -|Destination subscriber for given environment +|Destination subscriber for a given environment |* Consume messages from a destination. * Delete messages from a destination. | -| Destination publisher for given environment +| Destination publisher for a given environment |* Send messages to a destination. * Update message TTL on a destination. | diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 90f576c1..11be547f 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -4,11 +4,11 @@ Anypoint MQ is a multi-tenant, cloud-based message queuing service for exchangin The Anypoint MQ messaging broker enables applications to communicate by publishing a Mule message to a queue so that another app can consume the message. Anypoint MQ is fully integrated with Anypoint Platform, offering access control, client management, and connectors. -Integration with access management enables you to specify environments and business groups for +Integration with Access Management enables you to specify environments and business groups for role-based access control and support for connected apps. -Anypoint MQ supports hybrid use cases, IoT (Internet of Things) in which you collect data from different devices, -and provides a REST API to use with device applications. +Anypoint MQ supports hybrid use cases and IoT (Internet of Things), in which you collect data from different devices. +Anypoint MQ also provides a REST API for device applications. You can also use Anypoint MQ with other app frameworks such as node.js to communicate with queues. This spotlight video gives an overview of Anypoint MQ: diff --git a/modules/ROOT/pages/mq-access-management.adoc b/modules/ROOT/pages/mq-access-management.adoc index 2f8803d6..c89f0c1c 100644 --- a/modules/ROOT/pages/mq-access-management.adoc +++ b/modules/ROOT/pages/mq-access-management.adoc @@ -1,11 +1,11 @@ -= Setting Up the Environment and Access Permissions += Set Up the Environment and Access Permissions :imagesdir: ../assets/images/ -Create an environment and manage the roles of users who administer the Anypoint MQ features in Anypoint Platform for your organization using access management. +Create an environment and manage the roles of users who administer Anypoint MQ features in Anypoint Platform for your organization by using Access Management. == Before You Begin -* Create an environment with which to associate permissions. +* Create an environment for permissions. + Follow the steps in xref:access-management::environments.adoc#to-create-a-new-environment[To Create a New Environment]. * Make sure you have the <> required to use Anypoint MQ. @@ -21,6 +21,12 @@ To assign user permissions, follow the steps in xref:access-management::users.ad To use teams to assign permissions, follow the steps in xref:access-management::teams.adoc[]. +Anypoint MQ access is controlled at the environment and business group levels, not per individual queue or message exchange. + +Permissions such as *Destination Publisher* and *Destination Subscriber* are granted at the environment level and apply to all destinations in that environment. + +There is no native mechanism to restrict access to a single queue or message exchange. + //// == Give Users Anypoint MQ Access Permissions diff --git a/modules/ROOT/pages/mq-configure.adoc b/modules/ROOT/pages/mq-configure.adoc index a8ac212d..fdaea88e 100644 --- a/modules/ROOT/pages/mq-configure.adoc +++ b/modules/ROOT/pages/mq-configure.adoc @@ -6,7 +6,7 @@ Configure Anypoint MQ queues, exchanges, and connected apps to send and retrieve * xref:mq-access-management.adoc[] + -Use access management to create an environment and manage the roles of users who administer the Anypoint MQ features in Anypoint Platform for your organization. +Use Access Management to create an environment and manage the roles of users who administer Anypoint MQ features in Anypoint Platform for your organization. * xref:mq-queues.adoc[] + Create queues, FIFO queues, and dead-letter queues in Anypoint Platform. diff --git a/modules/ROOT/pages/mq-connected-apps.adoc b/modules/ROOT/pages/mq-connected-apps.adoc index 44a000e4..3383d8a1 100644 --- a/modules/ROOT/pages/mq-connected-apps.adoc +++ b/modules/ROOT/pages/mq-connected-apps.adoc @@ -2,8 +2,8 @@ The Connected Apps feature enables you to integrate external applications with Anypoint Platform by providing access to those applications without sharing your user credentials. -When you create a connected app, Access Management lists the ID and secret for the app. -You use the ID and secret values when configuring Anypoint Connector for MQ (Anypoint MQ Connector) in a Mule app in Anypoint Studio. +When you create a connected app, Access Management lists the client ID and client secret for the app. +You use the client ID and client secret values when configuring Anypoint Connector for MQ (Anypoint MQ Connector) in a Mule app in Anypoint Studio. include::partial$mq-versions.adoc[tags=mqConnectorVersion] For information about upgrading, see xref:anypoint-mq-connector::anypoint-mq-connector-upgrade-migrate.adoc[]. @@ -19,9 +19,9 @@ xref:access-management::connected-apps-developers.adoc[]. include::partial$mq-shared-connect-apps.adoc[tags=!ScopesConnAppTutorial] + -Use this ID and secret to get the access token required to authenticate with the Anypoint MQ API. +Use the client ID and client secret to get the access token required to authenticate with the Anypoint MQ API. -. When you configure Anypoint MQ Connector in your Mule app, paste the ID and secret values in the *Anypoint MQ Config* window in Studio: +. When you configure Anypoint MQ Connector in your Mule app, paste the client ID and client secret values in the *Anypoint MQ Config* window in Studio: + image::mq-tutorial-studio7-mq-config.png["Anypoint MQ Config window showing the URL, Client App ID, and Client Secret fields"] + diff --git a/modules/ROOT/pages/mq-faq.adoc b/modules/ROOT/pages/mq-faq.adoc index 8afccd3a..fce791bf 100644 --- a/modules/ROOT/pages/mq-faq.adoc +++ b/modules/ROOT/pages/mq-faq.adoc @@ -144,6 +144,12 @@ You can have the same object name for queues and exchanges in different environm You can use *Anypoint Platform* > *Access Management* > *Business Groups or Environments*. The queues and message exchanges created in a business group or environment are only visible to those with access to the business group or environment. +Anypoint MQ access is controlled at the environment and business group levels, not per individual queue or message exchange. + +Permissions such as *Destination Publisher* and *Destination Subscriber* are granted at the environment level and apply to all destinations in that environment. + +There is no native mechanism to restrict access to a single queue or message exchange. + == Can I use Anypoint MQ on-premises? You can publish a message from an on-premises system to Anypoint MQ and have another on-premises