Uploaded image for project: 'AMQ Interconnect'
  1. AMQ Interconnect
  2. ENTMQIC-2170

Optionally enforce access policy on connections established by the router

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 1.4.0.GA
    • None
    • Qpid Dispatch Router
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • Hide
      When the router opens a connection to an external AMQP container, you can now define policies that restrict the resources that the external container can access on the router. Previously, policies could only be applied to inbound connections. This meant that it was possible for external containers to open links to any address on the router (such as `$management`, for example).

      To define the resources that an external container can access over a connector, you must create a connector policy. For more information, see this example of a connector policy: https://issues.apache.org/jira/secure/attachment/12963435/DISPATCH-1288.txt.
      Show
      When the router opens a connection to an external AMQP container, you can now define policies that restrict the resources that the external container can access on the router. Previously, policies could only be applied to inbound connections. This meant that it was possible for external containers to open links to any address on the router (such as `$management`, for example). To define the resources that an external container can access over a connector, you must create a connector policy. For more information, see this example of a connector policy: https://issues.apache.org/jira/secure/attachment/12963435/DISPATCH-1288.txt .
    • Documented as Feature Request
    • IC-2019-03

    Description

      There are cases where router-initiated connections to external processes (using connectors) need to have enforcement of access policy from the external container.

      This could use the default policy, or an explicit policy name could be configured with the connector.

      Attachments

        Issue Links

          Activity

            People

              crolke@redhat.com Chuck Rolke (Inactive)
              tross1@redhat.com Ted Ross
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: