On Mon, Feb 21, 2011 at 8:57 PM, Senaka Fernando <[email protected]> wrote:
> > > On Mon, Feb 21, 2011 at 8:33 PM, Samisa Abeysinghe <[email protected]>wrote: > >> Is this a developer question or s user question? > > > From what I gathered, this is related to writing an authenticator. So, IMO, > this is a developer question. > >From what I understand, the requirement to authenticate users to a particular service in a specific manner and not to the mgt-console. This can be done through an Axis2 handler. Carbon authenticators are more towards providing custom ways of authenticating users to the management console. > > >> I am wondering if we should have an OT KB on this. > > > Thilina/Prabath, is it a common use-case for having to write an > authenticator? If so, +1 for a KB for the benefit of the developers. > +1 for a KB intended for developers. We have encountered a couple of cases, where users want to write custom authenticators. But we need to refine the existing APIs to make it more simpler. For example, after successfully authenticating we need to set certain parameters to the Carbon Context. This is common to all the authenticators and it should be a part of the API. But users have to specifically do that with the current implementation. Thanks, Thilina > Thanks, > Senaka. > >> >> >> On Mon, Feb 21, 2011 at 8:24 PM, Senaka Fernando <[email protected]> wrote: >> >>> Hi Manjula, >>> >>> For the benefit of the others, please do update this thread with the >>> summary of the offline discussion that we had on this. >>> >>> Thanks, >>> Senaka. >>> >>> On Mon, Feb 21, 2011 at 3:21 PM, Manjula Rathnayake >>> <[email protected]>wrote: >>> >>>> Hi all, >>>> >>>> I am completing the sqs based authentication handler, so once we have >>>> identified that the user is authenticated, >>>> what parameters should be set in carbon context to get the user name at >>>> a later time? >>>> >>>> The idea is that, >>>> 1. A user register with sqs service(user is given a secret id) >>>> 2. When user consume the service, set of headers are provided with a >>>> signature signed by the secret id. >>>> 3. An authentication handler verify the signature. >>>> 4. At the back-end, to connect to qpid, user name is needed. This is >>>> taken from CarbonContext.getCurrentContext().getUsername(). >>>> >>>> So setting up the user name is required after successful authentication. >>>> >>>> >>>> >>>> Thank you. >>>> >>>> -- >>>> Manjula Rathnayaka >>>> Software Engineer >>>> WSO2, Inc. >>>> Mobile:+94 77 743 1987 >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> *Senaka Fernando* >>> Product Manager - WSO2 Governance Registry; >>> Associate Technical Lead; WSO2, Inc.; http://wso2.com* >>> Member; Apache Software Foundation; http://apache.org >>> >>> E-mail: senaka AT wso2.com >>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>> Linked-In: http://www.linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2, Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://www.linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > -- Thilina Buddhika Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 77 44 88 727 blog : http://blog.thilinamb.com
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
