Hi All,
Any update on this?
Thanks,
Himasha
On Fri, Jun 7, 2019 at 6:31 PM Himasha Guruge wrote:
> Hi Isuru,
>
> What will our stance be against these deprecated features? We have a
> prospect who is interested in using priority executors and enqueue mediator
> for a use-case.
> Are we still
Hi Himasha,
We haven't seen any usage of Priority executors in the past and even our
Integration studio doesn't support it.
If someone really needs the functionality, we may have to closely look at
the requirement and come up with a solution.
Thanks.
On Tue, Jun 11, 2019 at 9:32 AM Himasha
Hi Johann,
On Mon, Jun 10, 2019 at 12:08 PM Johann Nallathamby wrote:
> *Meeting Notes - 30/5/2019*
>
> During the meeting for [1], we also identified some federated account
> linking improvements that are currently not supported in WSO2 IS.
>
> A single physical user may have a set of linked
Tested followings,
- Basic flow with import APIs
- Basic Auth
- Analytics file writing/ uploading/ APIM Dashboard visibility
No blockers found.
*[+] Stable - Go ahead and release*
Thanks,
Praminda
On Mon, Jun 10, 2019 at 2:01 PM Rajith Roshan wrote:
> Tested the following scenarios.
Tested following.
- Basic flow with JWT token
- Resource level throttling
- Request/ Response intercepting.
No blockers found.
*[+] Stable - Go ahead and release*
On Mon, Jun 10, 2019 at 4:26 PM Praminda Jayawardana
wrote:
> Tested followings,
>
>- Basic flow with import APIs
>- Basic
*Meeting Notes - 30/5/2019*
During the meeting for [1], we also identified some federated account
linking improvements that are currently not supported in WSO2 IS.
A single physical user may have a set of linked local accounts in WSO2
Identity Server. The same physical user may have one or more
*Meeting Notes - 30/5/2019*
*Use Case*
The most general form of this use case was identified as follows.
A single physical user may have more than one local account in one or more
user stores in WSO2 Identity Server.
In some use cases the credentials and attributes may be separated into
their
Tested the following scenarios.
- etcd support
- API level/resource level throttling for open API based API
- Application level throttling for imported APIs
- Override endpoint URLs
- Mutual SSL
No blockers found.
*[+] Stable - Go ahead and release*
Regards,
Hasunie
On Mon, Jun 10, 2019 at
Tested:
- Importing APIs with scopes
- basic CORS support
No blockers found.
*[+] Stable - Go ahead and release.*
On Mon, Jun 10, 2019 at 5:51 PM Menaka Jayawardena wrote:
> Tested following.
> - Basic flow with JWT token
> - Resource level throttling
> - Request/ Response intercepting.
>
>
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
Tested the following scenarios.
- Basic throttling
- Custom application throttling for open API based api and imported APIs
- Custom subscription throttling for imported APIs
- Global throttling
- Basic flow in dev first approach
- Load balance and fail over endpoints
No
11 matches
Mail list logo
