Hi all,
What we have currently decided is to add a property to the
APIAuthenticationHandler(in the synapse-config) which declares a Base64
encoded JSON object. This JSON object contains scopes and roles of all the
resources in the API. So that we can access the property value at the
handler and
>
> I think apimVersion should always have a value. Each release should have
> its default.
>
> restVersion only comes in handy if we want to use a microgateway with an
> APIM version that was released after the microgateway was released. This is
> the only use case where we will not know how to
Hi Amali,
How are we going to derive the Rest API version? Do we keep a mapping
between the APIM version and the Rest API version in the microgateway code
level? If so, do not we need to modify the microgateway code after each
APIM release?
If we only have the Rest API version in the config
I think apimVersion should always have a value. Each release should have
its default.
restVersion only comes in handy if we want to use a microgateway with an
APIM version that was released after the microgateway was released. This is
the only use case where we will not know how to derive the
Hi all,
This email is regarding the implementation of the solution to the coupling
issue in MicroGateway.
Now the toolkit-config.toml will look similar to the following:
apiMVersion = ""
restVersion = ""
publisherEndpoint = "https://localhost:9443/api/am/publisher/{version};
adminEndpoint =
Added comment there. I think bringing broker and reliable key/value store
both to address this complicate deployment and solutions.
Thanks,
sanjeewa.
On Thu, Feb 28, 2019 at 1:44 PM Sampath Rajapakshe wrote:
> Hi All,
>
> I have added the reviewed new approach as a comment to the Github issue.
Hi All,
I have added the reviewed new approach as a comment to the Github issue. [1]
[1] https://github.com/wso2/product-microgateway/issues/298
Thanks,
Sampath
On Wed, Feb 27, 2019 at 1:39 PM Nuwan Dias wrote:
>
>
> On Wed, Feb 27, 2019 at 12:54 PM Vanjikumaran Sivajothy
> wrote:
>
>>
I think this approach is better than pub/sub topic because in that case
when new gateway joins cluster it cannot get all updates at first time.
OAuth token to JWT token exchange not available today. What available is
requesting access token with openID scope. In that case we will issue
access
