Hi Ruwan,
On Fri, Mar 15, 2019 at 9:40 AM Ruwan Abeykoon wrote:
> Hi Prakhash,
>
> Adding query parameters to the current request has no effect as the
> authenticator prompt is always a redirection. Adding a value into
> redirection URL most probably exposes internal private data via URL.
>
Hi Prakhash,
Adding query parameters to the current request has no effect as the
authenticator prompt is always a redirection. Adding a value into
redirection URL most probably exposes internal private data via URL.
However you can consider adding a cookie to the response as an alternative.
Here
Hi Devs,
I'm trying to assign a query parameter to the request during the
authentication flow, but I couldn't find a reference on how to do this.
function onLoginRequest(context) {
if (context.request.params.prompt != null &&
context.request.params.prompt[0].equals("login")) {
Hi Srivathsan,
Thanks for your response. This was resolved.
Regards,
Sanjay
On Mon, Mar 11, 2019 at 3:38 PM Srivathsan Shanmuganathan <
srivath...@wso2.com> wrote:
> [Adding dev@wso2.org]
>
> On Mon, 11 Mar 2019, 18:53 Srivathsan Shanmuganathan wrote:
>
>> Hi Sanjay,
>> May I know which
On Thu, Mar 14, 2019 at 4:24 PM Nuwan Dias wrote:
> Just thinking out loud, is there by any chance a possibility to run just 1
> forever for any number of policies? Even if that means a redesign of the
> policies?
>
Still, we don't know the logic behind the forever syntax. If it starts a
new
Just thinking out loud, is there by any chance a possibility to run just 1
forever for any number of policies? Even if that means a redesign of the
policies?
On Thu, Mar 14, 2019 at 3:48 PM Rajith Roshan wrote:
>
>
> On Thu, Mar 14, 2019 at 3:21 PM Nuwan Dias wrote:
>
>>
>>
>> On Thu, Mar 14,
On Thu, Mar 14, 2019 at 3:21 PM Nuwan Dias wrote:
>
>
> On Thu, Mar 14, 2019 at 3:20 PM Rajith Roshan wrote:
>
>>
>>
>> On Thu, Mar 14, 2019 at 2:32 PM Nuwan Dias wrote:
>>
>>> What about the developer first approach? In that case we pre load the
>>> default policies to the gateway anyway
We have 2 remote ESB EI 6.4.0 instances in a cluster sending datas to analytics
worker.
Here is what I can reproduce
> start Analytics worker (EI package 6.4.0) with options -Xms6G -Xmx6G
I tested the worker with both java versions "1.8.0_162" and Java(TM) SE
Runtime Environment (build
On Thu, Mar 14, 2019 at 3:21 PM Nuwan Dias wrote:
>
>
> On Thu, Mar 14, 2019 at 3:20 PM Rajith Roshan wrote:
>
>>
>>
>> On Thu, Mar 14, 2019 at 2:32 PM Nuwan Dias wrote:
>>
>>> What about the developer first approach? In that case we pre load the
>>> default policies to the gateway anyway
On Thu, Mar 14, 2019 at 3:20 PM Rajith Roshan wrote:
>
>
> On Thu, Mar 14, 2019 at 2:32 PM Nuwan Dias wrote:
>
>> What about the developer first approach? In that case we pre load the
>> default policies to the gateway anyway since there is no indication of an
>> API being associated to a subs
On Thu, Mar 14, 2019 at 2:32 PM Nuwan Dias wrote:
> What about the developer first approach? In that case we pre load the
> default policies to the gateway anyway since there is no indication of an
> API being associated to a subs throttling policy.
>
I wonder in current implementation also how
On Thu, Mar 14, 2019 at 2:23 PM Rajith Roshan wrote:
> Hi all,
> Currently in microgateway(MGW) when we create the project directory we
> fetch all the subscription and application policies and we generate the
> source for each policy. In each policy there is ever running loop
> (forever), in
What about the developer first approach? In that case we pre load the
default policies to the gateway anyway since there is no indication of an
API being associated to a subs throttling policy.
On Thu, Mar 14, 2019 at 2:23 PM Rajith Roshan wrote:
> Hi all,
> Currently in microgateway(MGW) when
Hi all,
Currently in microgateway(MGW) when we create the project directory we
fetch all the subscription and application policies and we generate the
source for each policy. In each policy there is ever running loop
(forever), in back ground to update the throttle counters. But the issue
some of
14 matches
Mail list logo
