Hi Ragu, Maybe I have missed some conversations. But why do we have to put APIM components in GREG to get the registry rest API working (I mean why do we have to bundle and ship). I certainly understand that if you need API Management you can have APIM features but, registry rest API is just a bunch of rest endpoints you expose from the registry. If you want OAuth key management; expose it via an API, to get the application/access tokens. If some one need this API to be managed then at that point he can front it with APIM and get management aspect working.
What did I miss ? Regards, /Nuwan On Fri, May 10, 2013 at 5:38 PM, Sriragu Arudsothy <[email protected]> wrote: > Hai...! > > > The Registry REST API has been implemented as follows, > > 1) I am running an APIM instance with Greg. > > 2) Publish an API via API publisher and specifies the Registry REST API > endpoint as the Target endpoint url in the API publisher. > > 3) Subscriber Creates an Application which has the published API via API > store > > 4) end user who wants to use that application will generate the access > token for the application and access the Registry REST API endpoint via > published API. > > Is there anyway that we can embed minimal APIM component that can > accomplish the needs? > > Thanks...! > Ragu > > > > > > > _______________________________________________ > 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/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
