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/05/13 15:48:12 UTC
[jira] [Resolved] (DISPATCH-331) Allow for a default policy to
apply when open.hostname doesn't match an existing policy
[ https://issues.apache.org/jira/browse/DISPATCH-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke resolved DISPATCH-331.
----------------------------------
Resolution: Fixed
Fixed by commits 590d79e and 33cbeed
> Allow for a default policy to apply when open.hostname doesn't match an existing policy
> ---------------------------------------------------------------------------------------
>
> Key: DISPATCH-331
> URL: https://issues.apache.org/jira/browse/DISPATCH-331
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Policy Engine
> Affects Versions: 0.6.0
> Reporter: Ted Ross
> Assignee: Chuck Rolke
> Fix For: 0.6.0
>
>
> Add a feature to the policy engine that allows the deployer to specify a policy to be used for connections with no open.hostname or a hostname that does not match any existing policy.
> For users that don't wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.
--
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