On Tue, Mar 15, 2011 at 5:32 PM, Danushka Menikkumbura <[email protected]>wrote:
> The access key cannot be the username because it is a 20 digit key. See >> >> http://docs.amazonwebservices.com/AWSSimpleQueueService/2009-02-01/SQSGettingStartedGuide/ >> So we need to do something to make it fit that. >> > > When you sign up for an AWS account you get an auto-generated access key > and a secret key. > > I'm still not clear if the secret key is stored separately or just >> something we calculate from their existing password? >> > > We have to deal with two scenarios here IMO. Those who come through the WS > API and those who need to use Messageboxes in their Carbon components. For > the former I think we need to have a provisioning mechanism similar to AWS > account sign up. > The SQS service supports two types of authentication. 1. AWS specific authentication. 2. Carbon authentication. Uses who directly calls SQS API use the #1 option. For Admin console users use #2 option. In fact FE calls the SQS service and in this case users has already logged in. thanks, Amila. > > The bottom line is that auth/authz is handled by Qpid underneath using > Carbon user store manager and authorization manager. So the credentials > created at the time of SQS account creation (if we are going to support > that) should be transparent to the user store manager and the authz manager. > > Thanks, > Danushka > > _______________________________________________ > 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
