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/29 23:27:13 UTC
[jira] [Resolved] (DISPATCH-287) Policy does not allow
configuration for unspecified Open hostname
[ https://issues.apache.org/jira/browse/DISPATCH-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke resolved DISPATCH-287.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.6
Fixed at Commit 375c3ed
Note that the proton subsystem handling of Open Hostname is a *moving target*. In the past an open to 'localhost:5672' set a hostname of '0.0.0.0:5672'. Now the same open generates a blank hostname. In the future, the rules may change.
> Policy does not allow configuration for unspecified Open hostname
> -----------------------------------------------------------------
>
> Key: DISPATCH-287
> URL: https://issues.apache.org/jira/browse/DISPATCH-287
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine
> Affects Versions: 0.6
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
> Fix For: 0.6
>
>
> Currently if the hostname is blank when policy is in force then the connection is automatically disallowed. An improvement in this case would be to allow for some policy to be assigned.
> Policy is normally assigned based on the incoming connection's
> (username, client-host-ip, Open.hostname) tuple. This issue could be solved by allowing for blank Open.hostname in the policy definitions and run time.
--
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