Hi APIM team,
Is there a way to put transport headers coming from incoming request into
JWT [1] generated for backend service ?
[1]
https://docs.wso2.com/display/AM220/Passing+Enduser+Attributes+to+the+Backend+Using+JWT
Thanks,
Gayan
___
Dev mailing li
On Tue, Jul 3, 2018 at 11:26 AM Gayan Yalpathwala wrote:
> Hi Isura,
>
> I have encountered the same problem in IS 5.3.0 as well. The user account
> gets locked after 3 failed attempts, but gets unlocked after 5 minutes,
> whereas I need the account to be unlocked by the admin.
>
> Here are the c
Hi Isura,
I have encountered the same problem in IS 5.3.0 as well. The user account
gets locked after 3 failed attempts, but gets unlocked after 5 minutes,
whereas I need the account to be unlocked by the admin.
Here are the configuration values I have set in identity-event.properties.
account.l
This seems to be true.
@IS team, What is the reason to expire the token before the expiry time
and without a revocation request?
On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna wrote:
> In the latest release of API manager if we try to generate new access
> tokens before it expired using "pas
Thanks Maduranga and Fara
On Mon, Jul 2, 2018, 1:46 PM Maduranga Siriwardena
wrote:
> Yes [1] reported and WSO2-CARBON-PATCH-4.4.0-2411 is released to fix this
> issue.
>
> [1] https://github.com/wso2/product-is/issues/2982
>
> On Fri, Jun 29, 2018 at 2:07 PM Farasath Ahamed
> wrote:
>
>> C
Hi,
Below is a sample message the tool will provide when it detects that
there's no change from the server.
*First time running the setup command:*
$ micro-gw setup pizzaproj -a PizzaShackAPI -v 1.0.0 -f
Enter Password for admin:
Setting up project pizzaproj successful.
*Second time:*
$ micro-g
In the latest release of API manager if we try to generate new access
tokens before it expired using "password grant type " output is different
access tokens with the same refresh token. when checking the database it
shows the state is "EXPIRED" of the previous access token.
In earlier releases, i
Hi Devs,
This is with respect to [1] reported.
This issue has been occurred due to the fix done over [2] as per the
architectural discussion at [3].
Previously when an authentication request comes for an active session, in
each step we validated if the user has been authenticated over the
respect
+dev
On Mon, Jul 2, 2018 at 2:06 PM, Nilasini Thirunavukkarasu wrote:
> Hi,
>
> I am working on a UI change to support multiple certificate to IDP.
> According to my current implementation if we upload the multiple
> certificates the UI will look like as below. According to the discussion
> [1]
Yes [1] reported and WSO2-CARBON-PATCH-4.4.0-2411 is released to fix this
issue.
[1] https://github.com/wso2/product-is/issues/2982
On Fri, Jun 29, 2018 at 2:07 PM Farasath Ahamed wrote:
> Can you try this with a WUM updated pack?
> IIRC this is a known issue which is fixed now.
>
> On Fri, Jun
10 matches
Mail list logo