Hi Rajkumar,
You have mentioned that,
because the very first request to API Store will land on jaggery_acs.jag
> and since SSO properties are not there in SSO relaying party object, you
> will get NPE like below.
What do you mean by very first request? Is it before login to IDP? I guess,
Hi Abimaran,
I'm sorry I couldn't understand the context of what you are saying. I was
reporting that IDP initiated SSO is not working (login to IDP first and let
IDP to redirect user to SP).
Thanks.
On Thu, Jan 12, 2017 at 1:59 AM Abimaran Kugathasan
wrote:
> Hi Rajkumar,
Hi Rajkumar,
On Wed, Jan 11, 2017 at 11:08 PM, Rajkumar Rajaratnam
wrote:
> IDP initiated SSO for Store is also not working. Should be the same case
> with Publisher. Reason for this issue is as below.
>
> For SP initiated SSO, we read SSO properties from site.json and set
IDP initiated SSO for Store is also not working. Should be the same case
with Publisher. Reason for this issue is as below.
For SP initiated SSO, we read SSO properties from site.json and set them to
SSO relaying party object in sso/filter [1].
For IDP initiated SSO, the same thing should be
Hi all,
We are calling off the vote due to the problems found in stat graphs. We
will do a RC3 soon.
Thanks!
Malintha
On Wed, Jan 11, 2017 at 12:01 PM, Abimaran Kugathasan
wrote:
> Tested Endpoints, Throttling and general API invocations scenarios
>
> [+] Stable - go ahead
Tested Endpoints, Throttling and general API invocations scenarios
[+] Stable - go ahead and release
On Wed, Jan 11, 2017 at 11:20 AM, Praminda Jayawardana
wrote:
> Tested client SDK generation for super tenant, non admin, tenant and self
> signup users.
>
> [+] Stable - go
Tested client SDK generation for super tenant, non admin, tenant and self
signup users.
[+] Stable - go ahead and release
On Wed, Jan 11, 2017 at 10:56 AM, Arshardh Ifthikar
wrote:
> Tested the Websocket API feature
>
> [+] Stable - go ahead and release
>
> On Wed, Jan 11,
Tested the Websocket API feature
[+] Stable - go ahead and release
On Wed, Jan 11, 2017 at 10:52 AM, Tharindu Dharmarathna
wrote:
> Tested the Blocking condition and Advance throtting feature
>
> [+] Stable - go ahead and release
>
>
> On Wed, Jan 11, 2017 at 10:50 AM,
Tested the Blocking condition and Advance throtting feature
[+] Stable - go ahead and release
On Wed, Jan 11, 2017 at 10:50 AM, Chamila Adhikarinayake
wrote:
> Tested workflows for API lifecycle state change feature.
>
> [+] Stable - go ahead and release
>
> On Tue, Jan 10,
Tested workflows for API lifecycle state change feature.
[+] Stable - go ahead and release
On Tue, Jan 10, 2017 at 4:35 PM, Malintha Amarasinghe
wrote:
> Hi All,
>
> This is the 2nd Release Candidate of WSO2 API Manager 2.1.0
>
> Please download, test the product and vote.
10 matches
Mail list logo