Hi,
Thanks for the information Darshana. Didn't know it was decided to be
rectified in an RC2.
Thanks for the fix.
On Thu, Mar 15, 2018 at 1:39 AM, Omindu Rathnaweera wrote:
> Hi Lanka,
>
> This issue is now fixed in the latest oauth version (v5.6.63) and will be
> available
Hi Lanka,
This issue is now fixed in the latest oauth version (v5.6.63) and will be
available with RC2.
Regards,
Omindu.
On Wed, Mar 14, 2018 at 10:32 PM, Darshana Gunawardana
wrote:
> Hi Lanka,
>
> As you already know, we are working on rectifying this NPE in the RC2.
>
>
Hi Lanka,
As you already know, we are working on rectifying this NPE in the RC2.
Thanks,
On Wed, Mar 14, 2018 at 10:25 PM, Pushpalanka Jayawardhana
wrote:
> Hi,
>
> On Wed, Mar 14, 2018 at 10:14 PM, Pushpalanka Jayawardhana > wrote:
>
>>
>>
>> On Wed, Mar 14,
Hi,
On Wed, Mar 14, 2018 at 10:14 PM, Pushpalanka Jayawardhana
wrote:
>
>
> On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana > wrote:
>
>> Hi All,
>>
>> Tested OIDC hybrid flow with "code idtoken" response type. This is
>> breaking with "Invalid
On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana
wrote:
> Hi All,
>
> Tested OIDC hybrid flow with "code idtoken" response type. This is
> breaking with "Invalid response type" error message.
> Could do a bit of debugging and it seems that at [1], it failing to
>
Hi All,
Tested OIDC hybrid flow with "code idtoken" response type. This is breaking
with "Invalid response type" error message.
Could do a bit of debugging and it seems that at [1], it failing to
identify the existing key for "code idtoken" type.
In the HashTable returned at
On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya
wrote:
> Hi Sagara,
>
> Yes I have suggested other teams also to follow the IS convention in [1].
> APIM team told me offline that they already changed. Hope others will do
> the same.
>
Great.
Thanks !
>
> [1] [GDPR]
On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya
wrote:
> Hi Sagara,
>
> Yes I have suggested other teams also to follow the IS convention in [1].
> APIM team told me offline that they already changed. Hope others will do
> the same.
>
Great.
Thanks !
>
> [1] [GDPR]
Hi Sagara,
Yes I have suggested other teams also to follow the IS convention in [1].
APIM team told me offline that they already changed. Hope others will do
the same.
[1] [GDPR] Anonymization Tool default configurations/references are
differed over the Products
Thanks!
*Jayanga Kaushalya*
On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara wrote:
> Hi all,
>
> We are calling-off this vote as we have found an issue,
>
>- for user-mgt ui component in EI product
>- in Windows environment
>
> Since we want to align same component versions among EI & IS, we will
Hi all,
We are calling-off this vote as we have found an issue,
- for user-mgt ui component in EI product
- in Windows environment
Since we want to align same component versions among EI & IS, we will fix
this and update versions in IS as well. Additionally we will fix the issue
in
Hi,
I have tested the following flows in mysql.
- User management, role management (Primary + Secondary user store)
- OIDC flow (password grant, authorization code)(Primary + Secondary
user store)
- consent management with SAML SSO for primary and secondary users.
- SAML assertion
Hi Dilini,
We will fix this, if we noted any blocker for RC1 release.. If not, let's
continue on the vote considering this is a known issue..
Thanks,
On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake wrote:
> Hi,
>
> The README .txt contains references to old documentation
Hi,
The README .txt contains references to old documentation and few other
issues which is reported in [1]. Better if we can fix those. WDUT?
[1] https://github.com/wso2/product-is/issues/2945
Regards,
Dilini
On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed wrote:
>
>
14 matches
Mail list logo