On Wed, Nov 16, 2016 at 12:25 PM, Hasintha Indrajee
wrote:
>
>
> On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee
> wrote:
>
>> Hi all,
>>
>> Please find the below fix for this issue. This includes an API change.
>> Please review and merge this fix.
>>
>>
Noted Malaka.
On Wed, Nov 16, 2016 at 11:35 AM, Malaka Silva wrote:
> Hi Thulasika,
>
> As we discussed offline please check the fix.
>
> On Wed, Nov 16, 2016 at 10:30 AM, Farasath Ahamed
> wrote:
>
>> Hi Malaka/Thulasika,
>>
>> Since we can't fix this for
On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee
wrote:
> Hi all,
>
> Please find the below fix for this issue. This includes an API change.
> Please review and merge this fix.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/10
>
This fix only
Hi Thulasika,
As we discussed offline please check the fix.
On Wed, Nov 16, 2016 at 10:30 AM, Farasath Ahamed
wrote:
> Hi Malaka/Thulasika,
>
> Since we can't fix this for IS 5.2.0 now as it is already released. Shall
> we fix it from JWT bearer grant connector side for IS
Hi Malaka/Thulasika,
Since we can't fix this for IS 5.2.0 now as it is already released. Shall
we fix it from JWT bearer grant connector side for IS 5.2.0 only?
Otherwise, we won't have a JWT connector that is working with IS 5.2.0.
WDYT?
Thanks,
Farasath Ahamed
Software Engineer, WSO2 Inc.;
yes Malaka, It doesn't work with fresh 5.2.0 pack.
On Tue, Nov 15, 2016 at 1:57 PM, Malaka Silva wrote:
> If this does not work with fresh pack we can't say it's supported.
>
> On Tue, Nov 15, 2016 at 9:38 AM, Thulasika Vijayanathan <
> thulas...@wso2.com> wrote:
>
>> Hi,
>>
>>
Hi Kathees,
Before releasing this can you please check whether claim mappings are
working ? ie if we configure a different subject claim it should be there
as the subject. I think this is a valid basic requirement.
On Wed, Nov 16, 2016 at 9:44 AM, Kathees Rajendram wrote:
>
Yes. Will release a version of CAS inbound with this fix.
Thanks,
Kathees
On Wed, Nov 16, 2016 at 8:22 AM, Malaka Silva wrote:
> Hi Kathees,
>
> Can you check this and release the fix to store please?
>
> On Tue, Nov 15, 2016 at 10:36 PM, Kanapriya Kuleswararajan <
>
Hi Kathees,
Can you check this and release the fix to store please?
On Tue, Nov 15, 2016 at 10:36 PM, Kanapriya Kuleswararajan <
kanapr...@wso2.com> wrote:
> Hi Malaka,
>
> I have tested existing cas-inbound-authenticator by enable the SaaS
> application in super tenant domain and try to login
Hi Malaka,
I have tested existing cas-inbound-authenticator by enable the SaaS
application in super tenant domain and try to login from different tenant
domain. But I couldn't login with different tenant domain.
I checked with above fix also, It works fine when the application is a SaaS
app.
Hi all,
Please find the below fix for this issue. This includes an API change.
Please review and merge this fix.
[1] https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/10
On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva wrote:
> Kanapriya can you have a quick look
Kanapriya can you have a quick look and update with findings please?
On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee
wrote:
> Hi All,
>
> CAS is not working when we register a SaaS application and when I am
> trying to login from a different tenant user. This should be
If this does not work with fresh pack we can't say it's supported.
On Tue, Nov 15, 2016 at 9:38 AM, Thulasika Vijayanathan
wrote:
> Hi,
>
> I have applied this fixed as a patch in 5.2.0 it works.
>
> Thanks,
> Thulasika.
>
> On Mon, Nov 14, 2016 at 12:25 AM, Farasath Ahamed
13 matches
Mail list logo