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

Rajith Attapattu commented on QPID-2476:
----------------------------------------

Andrew,

Great to see you working on the ACL stuff.
In view of keeping functionality/behaviour the same btw C++ and Java Broker, I 
would appreciate if the above items are discussed on the mailing list.
I am also planning to work on some of the items listed above.
I look forward to discussing these items on the list with you.

Regards,

Rajith 

> Complete ACL implementation for 0-10 code path
> ----------------------------------------------
>
>                 Key: QPID-2476
>                 URL: https://issues.apache.org/jira/browse/QPID-2476
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: 0.7
>            Reporter: Andrew Kennedy
>             Fix For: 0.7
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Complete ACL implementation for 0-10 code path, providing an ACLv2 
> implementation that covers the following features/requirements:
> - Best practice security design
> - Support for roles/groups
> - Appropriate for standard stores for authorisation credentials (e.g. LDAP, 
> Kerberos)
> - Expressable as XML
> - Easy to store/backup/extract ACL config
> - Exception handling catching at point of ACL application and return to 
> client via Connection ExceptionListener with correct error code, log failure 
> in broker
> - No significant performance cost on publish, permissions to be cached
> - Security handled at correct level of abstraction internally
> - Interoperability with existing ACLv2

-- 
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