On Thu, Jan 10, 2013 at 5:30 PM, Senaka Fernando <[email protected]> wrote:
> Hi Nuwan, > > Reviews are not done offline, :). Ragu will post details of the review > once we are ready and please do join so that we can validate this API > against the UES use-cases. > will do. > > Thanks, > Senaka. > > On Thu, Jan 10, 2013 at 4:50 PM, Nuwan Bandara <[email protected]> wrote: > >> Hi, >> >> If we are doing this, we will have to do it in a generic manner, so that >> later on other platform APIs also can be exposed in the same manner. For an >> example, wight now if we extend the AbstractAdmin, in any of our admin >> service we are sure that the service is secured over basic OAuth. similar >> manner this has to be done IMO. >> >> I would like to join any reviews/discussions, if anything is happening >> offline >> >> Regards, >> /Nuwan >> >> >> On Thu, Jan 10, 2013 at 11:17 AM, Senaka Fernando <[email protected]>wrote: >> >>> Hi Ragu, >>> >>> OAuth is not strictly a part of IS according to my understanding. It is >>> a reusable component in our platform, and we should be able to make use of >>> it without much of a hassle. >>> >>> Thanks, >>> Senaka. >>> >>> >>> On Thu, Jan 10, 2013 at 11:16 AM, Sriragu Arudsothy <[email protected]>wrote: >>> >>>> Hai Senaka, >>>> >>>> OAuth not yet implemented. I will do that first. I >>>> think OAuth is mainly implemented in IS. I think I have to implement the >>>> integration part of the OAuth to the rest api. Please tell me your ideas >>>> how can I approach this situation? >>>> >>>> What else I need to be considered when implement this? >>>> >>>> Ragu >>>> >>>> >>>> On Thu, Jan 10, 2013 at 11:03 AM, Senaka Fernando <[email protected]>wrote: >>>> >>>>> Hi Ragu, >>>>> >>>>> Is OAuth based security implemented for this? If not, lets do that >>>>> first. Once done, lets have a review of the design and the code. Next step >>>>> would be to document the entire API and provide some sample(s) explaining >>>>> how this can be used. >>>>> >>>>> Thanks, >>>>> Senaka. >>>>> >>>>> >>>>> On Thu, Jan 10, 2013 at 10:13 AM, Sriragu Arudsothy >>>>> <[email protected]>wrote: >>>>> >>>>>> Hai All, >>>>>> >>>>>> >>>>>> The REST API currently implemented as a web - application. >>>>>> The web application get an remote registry instance to access the >>>>>> registry >>>>>> components. The current implementation does the necessary resource >>>>>> related >>>>>> operations using the instance of the remote registry. eg( adding >>>>>> comments/rating/tags ..etc on the resource). >>>>>> >>>>>> After I had the offline chat with G-Reg team, we now plan to move the >>>>>> REST api into the platform/registry components as a separate OSGI >>>>>> bundle. I >>>>>> did the necessary changes to the current app and moved to the above >>>>>> location and checked whether the REST api bundle is active/enabled when >>>>>> the >>>>>> G-Reg instance is started. Yes, it was enabled. >>>>>> >>>>>> I would like to know your opinion on how the REST API implementation >>>>>> need to be adapted to G-Reg. or How Do I need to implement this REST API >>>>>> by >>>>>> means some other products also can access? >>>>>> >>>>>> Thanks! >>>>>> Regards, >>>>>> Sriragu >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> * <http://wso2con.com/> >>>>> * >>>>> * >>>>> >>>>> Senaka Fernando* >>>>> Member - Integration Technologies Management Committee; >>>>> 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://linkedin.com/in/senakafernando >>>>> >>>>> *Lean . Enterprise . Middleware >>>>> >>>> >>>> >>> >>> >>> -- >>> * <http://wso2con.com/> >>> * >>> * >>> >>> Senaka Fernando* >>> Member - Integration Technologies Management Committee; >>> 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://linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Thanks & Regards, >> >> Nuwan Bandara >> Associate Technical Lead & Member, MC, Development Technologies >> WSO2 Inc. - lean . enterprise . middleware | http://wso2.com >> blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >> 9629 >> * >> <http://www.nuwanbando.com/> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > * <http://wso2con.com/> > * > * > > Senaka Fernando* > Member - Integration Technologies Management Committee; > 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://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > -- *Thanks & Regards, Nuwan Bandara Associate Technical Lead & Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
