[ https://issues.apache.org/jira/browse/DISPATCH-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267373#comment-15267373 ]
ASF subversion and git services commented on DISPATCH-287: ---------------------------------------------------------- Commit 9dede38ce660293f9ffad78028d2b68bd8d381cc in qpid-dispatch's branch refs/heads/master from [~chug] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=9dede38 ] DISPATCH-287: Allow management access from 'localhost', '0.0.0.0', and ''. This forgives dispatch tools underlying connection support variances until the tools can go to a specific application/hostname on demand. > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org