Hi all,
There is a requirement to add the following features to the Microgateway in
Future.
1.
Add multiple APIs to a project
2.
Publish APIs from Microgateway to Store
3.
Support fine-grained endpoint configurations based on resource level.
-
Ex. GET menu -
Hi,
> *Hi,*
>
> *micro-gw set-project *
> I think setting the project name we can do within the *micro-gw setup*
> command itself rather having another command.
> *micro-gw setup -a -oa -e
> *
>
Yes, we can do that in this case. But if you want to switch between
different projects, we can't u
Hi,
I think the commands
*micro-gw setup , *
*and *
*micro-gw setup -a -oa -e
*
should be a single command when user already has a swagger. When we use
the second command it should create project structure as well as API
details as well. We don't need initial setup command to create project
Hi all,
>From the commands mentioned above, setup command and build command will be
implemented in the newly proposed way as a start. For setup command, it
needs to be compatible for OpenAPI spec 2.0 as well as 3.0. Therefore we
take basepath as a command line argument when the OpenAPI version is
Will change the endpoint configuration as suggested by @Pubudu Gunatilaka
. It seems to be more convenient in terms of user
experience.
Thank you,
Viraj
On Thu, Mar 21, 2019 at 3:49 PM Viraj Gamage wrote:
> Hi Pubudu,
>
> IMO, It doesn't seem possible to bring all three f
Tested the following scenarios.
- disabling security in resource level and API level
- override "x-wso2-disable-security"
- resource level endpoints (HTTP, load-balance, and failover)
No blockers found.
*[+] Stable - Go ahead and release*
Regards,
Viraj
On Mon, Jun 10, 2019 at 6:32 PM Hasunie A
Hi all,
gRPC is a modern, open-source remote procedure call (RPC) framework. Due to
the advantages in terms of performance and usability, grpc is becoming
popular these days. The idea is to provide support for grpc in
microgateway. As the initial step, we would consider the scenario where
both the
Hi All,
Tested the following.
- Import API to Microgateway Project
- Analytics with Microgateway
- Microgateway Analytics Report Generation.
No issues found.
[+] Stable - go ahead and release
Regards,
Viraj
On Sun, Mar 22, 2020 at 10:23 PM Rukshan Premathunga
wrote:
> Hi All,
>
> T
Hi all,
Tested the following.
- Global throttling for application policies, subscription policies,
resource level policies, and api level policies
- Analytics event publishing via File upload method
- Analytics event publishing using gRPC
No issues found.
*[+] Stable - Go ahead and r
Hi all,
Tested the following scenarios.
- Invoke APIs using JWT/ JTI claim with APIM 3.2.0
- Check scopes functionality using JWT/ JTI claim with APIM 3.2.0
- Subscription Validation using JWT/JTI claim with APIM 3.2.0
- JWTs with JWKS endpoint
- JWTs from Third party STS
- Larg
Hi All,
Tested the following scenarios with Microgateway 3.2.0-rc2 distribution.
- Import APIs to the microgateway project.
- Invoke APIs with JWT with subscription validation enabled/disabled.
- Invoke APIs with JTI Claim with subscription validation
enabled/disabled. (using Token in
Hi all,
Tested the following scenarios.
- JWT Authentication with APIM 3.1.0 and 3.2.0 both. (using JWKs
endpoint and Certificate within truststore)
- Subscription validation with APIM 3.1.0 and 3.2.0 both.
- Authentication using JTI claim in 3.2.0 (with and without subscription)
-
12 matches
Mail list logo
