You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2016/04/01 16:25:25 UTC
[jira] [Resolved] (DISPATCH-188) Dispatch needs a policy mechanism
to limit user connections and activity
[ https://issues.apache.org/jira/browse/DISPATCH-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke resolved DISPATCH-188.
----------------------------------
Resolution: Fixed
This feature has landed.
> Dispatch needs a policy mechanism to limit user connections and activity
> ------------------------------------------------------------------------
>
> Key: DISPATCH-188
> URL: https://issues.apache.org/jira/browse/DISPATCH-188
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container, Management Agent
> Affects Versions: 0.5
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
> Fix For: 0.6
>
>
> At a minimum this should support
> * a framework for a Policy Authority external to Dispatch
> ** holds policy configuration
> ** provides policy allow/deny decisions at run time
> * connection approval/denial based on authorized user name
> * per-user connection count limits and grand total connection count limits
> * management interface to expose statistics and live connection state
> Further enhancements to connection limits should support
> * connections limited by
> ** user host IP
> ** Dispatch router name and port
> ** AMQP Open frame contents
> Further enhancements to policy should support
> * limits to link creation source and target address names
> * multitenancy
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org