Can you explain the role of the Publisher and Store? Why do we push the API
to the publisher? Are we going to use the Store in any use-case?
On Wed, Sep 21, 2016 at 3:15 PM, Senthalan Kanagalingam
wrote:
> Yes, When the end user using APIs from the Application server the
>
Hi Ajanthan,
The integrated API gateway is doing only the OAuth authorization. But the
idea of the integrated API gateway is to provide API Management
capabilities without another network hop.
Thanks and regards,
Senthalan
On Tue, Sep 20, 2016 at 11:36 PM, Ajanthan Balachandran
Yes, When the end user using APIs from the Application server the
integrated gateway will take care of authorization. It will only use the
key manager of API Manager to validate.
On Wed, Sep 21, 2016 at 3:04 PM, Nuwan Dias wrote:
> But in that case the Gateway component in the
In Publisher the API developers creates APIs and and publish them into
Store.
In Store the end users can subscribe those APIs and use them.
According to this scenario, there is no use case for API Store. Because we
are going to automatically create APIs of the deployed web apps in API
publisher.
But in that case the Gateway component in the API Manager is not required
isn't it?
On Wed, Sep 21, 2016 at 2:37 PM, Senthalan Kanagalingam
wrote:
> Hi Ajanthan,
>
> The integrated API gateway is doing only the OAuth authorization. But the
> idea of the integrated API
Hi Senthalan,
For api publishing you have suggested that the api creator needs to create
an OAuth app and configure that with the server. Cant we make it more
seamless integration by only configuring a user and call the dynamic
client registration endpoint to create an app.
In addition I am
Smaeera, are these things we can fix?
--Srinath
On Thu, Sep 22, 2016 at 11:23 AM, Nuwan Dias wrote:
> Hi,
>
> This is to raise some concerns over the current server profiles. Although
> we are able to control the bundles which are loaded to the runtime based on
> the -Dprofile
Hi,
This is to raise some concerns over the current server profiles. Although
we are able to control the bundles which are loaded to the runtime based on
the -Dprofile parameter, we still lack the ability of removing files and
modifying configuration files when the server starts on a profile. And