qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ChugR <...@git.apache.org>
Subject [GitHub] qpid-dispatch pull request #255: DISPATCH-333: Create new router policies do...
Date Fri, 02 Mar 2018 15:46:18 GMT
Github user ChugR commented on a diff in the pull request:

    --- Diff: doc/new-book/configuration-security.adoc ---
    @@ -412,3 +414,356 @@ listener {
     For more information about these attributes, see xref:adding_sasl_authentication_to_incoming_connection[].
    +== Authorizing Access to Messaging Resources
    +You can restrict the number of user connections, and control access to AMQP messaging
resources by configuring _policies_.
    +=== Types of Policies
    +You can configure two different types of policies: _global policies_ and _vhost policies_.
    +Global policies::
    +Settings for the router. A global policy defines the maximum number of incoming user
connections for the router (across all vhost policies), and defines how the router should
use vhost policies.
    +Vhost policies::
    +Connection and AMQP resource limits for a messaging endpoint (called an AMQP virtual
host, or _vhost_). A vhost policy defines what a client can access on a messaging endpoint
over a particular connection.
    +A vhost is typically the name of the host to which the client connection is directed.
For example, if a client application opens a connection to the `amqp://mybroker.example.com:5672/queue01`
URL, the vhost would be `mybroker.example.com`.
    +The resource limits defined in global and vhost policies are applied to user connections
only. The limits do not affect inter-router connections or router connections that are outbound
to waypoints.
    +=== How {RouterName} Applies Policies
    +When a client connects to a router, the router determines whether to permit the connection
based on the global and vhost policies, and the following properties of the connection:
    +* The host to which the connection is directed (the vhost)
    +* The connection's authenticated user name
    +* The host from which the client is connecting (the remote host)
    +If the connection is permitted, then the router applies a vhost policy that matches the
vhost to which the connection is directed. The vhost policy limits are enforced for the lifetime
of the connection.
    +=== Configuring Global Policies
    +You can set the incoming connection limit for the router and define how it should use
vhost policies by configuring a global policy.
    +* In the router configuration file, add a `policy` section.
    +policy = {
    +    maxConnections: 10000  // <1>
    +    enableVhostPolicy: true  // <2>
    +    policyDir: /etc/qpid-dispatch/policies/  // <3>
    +    defaultVhost: $default  // <4>
    +<1> The maximum number of concurrent client connections allowed for this router.
This limit is always enforced, even if no other policy settings have been defined. The limit
is applied to all incoming connections regardless of remote host, authenticated user, or targeted
vhost. The default value is `65535`.
    --- End diff --
    maxConnections is restricted to be in the range 0..65535 inclusive. That said, a setting
of zero works but it renders the router to be useless as no users or management clients can
connect to it. The 65535 was chosen to be some limit that is probably not achievable in the
real world. 


To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message