You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (Reopened) (JIRA)" <ji...@apache.org> on 2012/02/02 09:07:53 UTC

[jira] [Reopened] (APLO-136) Broker complains when a dot is used in a dsub name

     [ https://issues.apache.org/jira/browse/APLO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lionel Cons reopened APLO-136:
------------------------------


The fix breaks access control :-(

My config allows the guest user to use destinations starting with test.

  <access_rule allow="guests" action="create destroy send receive consume" kind="topic queue dsub" id_regex="test\..*"/>

When using such a dsub, the (guest) client gets an error:

Not authorized to create the dsub 'test%2embtf%2ebb%2e2e339246%2ec1'. Principals=[org.apache.activemq.jaas.GroupPrincipal:guests, org.apache.activemq.jaas.UserPrincipal:guest]

FWIW, the same test was working fine with previous snapshots.
                
> Broker complains when a dot is used in a dsub name
> --------------------------------------------------
>
>                 Key: APLO-136
>                 URL: https://issues.apache.org/jira/browse/APLO-136
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: apollo-1.0-20120124.204817-255
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.0
>
>
> The user manual states that: "Destination names are restricted to using the characters a-z, A-Z, 0-9, _, - %, ~, ' ', or . in addition to composite separator , and the wild card *.".
> But when using a dot in a dsub, I get:
> 2012-01-25 08:20:15,588 | WARN  | org.apache.activemq.apollo.util.path.PathParser$PathException: Invalid destination: 'test.mbtf.bb.e37a3633.c2', it does not match regex: [ a-zA-Z0-9\_\-\%\~]+ | org.apache.activemq.apollo.broker.Broker | hawtdispatch-DEFAULT-1
> Could dots be allowed in dsub too?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira