[ 
https://issues.apache.org/jira/browse/QPID-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866586#action_12866586
 ] 

Rajith Attapattu commented on QPID-2600:
----------------------------------------

"However currently the c++ broker doesn't treat the '@' as optional as we do 
have the concept of a domain. "  should be changed as
However currently the c++ broker doesn't treat the '@' as optional as we do 
have the concept of a realm. 

> ACL policy doesn't permit certain characters in usernames added to groups
> -------------------------------------------------------------------------
>
>                 Key: QPID-2600
>                 URL: https://issues.apache.org/jira/browse/QPID-2600
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.6
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>            Priority: Minor
>             Fix For: 0.7
>
>
> Description of problem:
> Unable to add a host principle to a group, the acl policy file fails to load 
> and prevents qpidd from running.
> I guess this is partly due to us not figuring out what is exactly allowed for 
> group and usernames.
> How reproducible:
> Fails every time.
> Steps to Reproduce:
> 1. Add a host or service principle to a group in the acl file. Something like
> this will suffice:
>   group somegroup host/[email protected]
> Actual results:
> Failure to start. Error message is:
> Daemon startup failed: Could not read ACL file ACL format error:
> /etc/qpid/policy.acl:25: Name "host/[email protected]"
> contains illegal characters.
> Expected results:
> Should load and parse the group cleanly.    

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to