On Tue, Mar 15, 2011 at 2:30 PM, Paul Fremantle <[email protected]> wrote:
> 1) I'm still having trouble building :-( > > 2) Is there a way we can display the "amqp://etc" url for the queue in the > List Queues page? This would help coders a LOT getting it right. > +1. > > 3) At the moment, the queue permissions are based on users, for all > aspects. > a) This just won't work when this is plugged into LDAP. We need another > approach. > we use the UserManager and Autherization Manager APIs. I think even currently we have embedded LDAP and it works fine. > b) I agree that MessageBox and JMS-Created queues should have user based > permissions, but if I create a queue via the admin console, permissions > should be based on role. > +1. We can add role based authorization as well to the queues. > c) Even when its based on user the column title says "Role" > that is a bug :) > > 3) I don't understand the SQS secret key part. > a) I'd expect to see both an access key and a secret key > b) I don't expect the user to change these: I thought they were going to be > calculated. > Currently we use the user name as the access key. And also we let users to enter what ever secret key they like without just limiting to what by default we provide. We can change this to generate a access key and a secret key which is read only. thanks, Amila. > > More feedback when I finally get it to build :-) > > Paul > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > Office: +44 844 484 8143 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other confidential > information and is intended exclusively for the addressee/s. If you are not > the intended recipient/s, or believe that you may have received this > communication in error, please reply to the sender indicating that fact and > delete the copy you received and in addition, you should not print, copy, > retransmit, disseminate, or otherwise use the information contained in this > communication. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
