On Thu, Mar 23, 2017 at 10:21 PM, Pushpalanka Jayawardhana
wrote:
>
>
> On Fri, Mar 24, 2017 at 10:14 AM, Prabath Siriwardena
> wrote:
>
>> Well... I doubt we should make it configurable... Its the claim dialect
>> for the WSO2 products (or IS)... In any federation scenario - we do support
>> cl
On Fri, Mar 24, 2017 at 10:14 AM, Prabath Siriwardena
wrote:
> Well... I doubt we should make it configurable... Its the claim dialect
> for the WSO2 products (or IS)... In any federation scenario - we do support
> claim mappings for custom dialects...
>
One advantage Omindu highlighted in this t
Well... I doubt we should make it configurable... Its the claim dialect for
the WSO2 products (or IS)... In any federation scenario - we do support
claim mappings for custom dialects...
Thanks & regards,
-Prabath
On Thu, Mar 23, 2017 at 9:14 PM, Pushpalanka Jayawardhana
wrote:
>
>
> On Fri, Mar
On Fri, Mar 24, 2017 at 9:18 AM, Sagara Gunathunga wrote:
>
>
> On Thu, Mar 23, 2017 at 12:27 PM, Pushpalanka Jayawardhana > wrote:
>
>>
>>
>> On Tue, Mar 21, 2017 at 10:56 AM, Godwin Shrimal wrote:
>>
>>> If we make native claim dialect configurable, will product work by
>>> changing to differ
On Thu, Mar 23, 2017 at 12:27 PM, Pushpalanka Jayawardhana
wrote:
>
>
> On Tue, Mar 21, 2017 at 10:56 AM, Godwin Shrimal wrote:
>
>> If we make native claim dialect configurable, will product work by
>> changing to different claim dialect ?
>>
> That should be the expectation if we make the nati
On Tue, Mar 21, 2017 at 10:56 AM, Godwin Shrimal wrote:
> If we make native claim dialect configurable, will product work by
> changing to different claim dialect ?
>
That should be the expectation if we make the native claim dialect
configurable.
As of now, we have the native dialect hard coded
If we make native claim dialect configurable, will product work by changing
to different claim dialect ?
Thanks
Godwin
On Mon, Mar 20, 2017 at 4:34 PM, Pushpalanka Jayawardhana
wrote:
> +Prabath
>
> On Mon, Mar 20, 2017 at 4:33 PM, Pushpalanka Jayawardhana
> wrote:
>
>> Hi All,
>>
>> Have we
Hi All,
Have we made a conclusion on this? Are we expecting to make the native
dialect configurable?
Given that we have claim mapping functionality this won't be a mandatory
requirement. But this has the advantage Omindu mentioned against the
complexities introduced by letting this configurable fo
+Prabath
On Mon, Mar 20, 2017 at 4:33 PM, Pushpalanka Jayawardhana
wrote:
> Hi All,
>
> Have we made a conclusion on this? Are we expecting to make the native
> dialect configurable?
> Given that we have claim mapping functionality this won't be a mandatory
> requirement. But this has the advant
One of the advantages would be that we can avoid the overhead of claim
transformation.
Regards,
Omindu.
On Thu, Feb 23, 2017 at 1:53 PM, Omindu Rathnaweera wrote:
> Do we need to make the native claim dialect configurable ? AFAIK it is not
> configurable and we are using a hardcoded constant fo
Do we need to make the native claim dialect configurable ? AFAIK it is not
configurable and we are using a hardcoded constant for the dialect URI (
http://wso2.org/claims).
Regards,
Omindu
--
Omindu Rathnaweera
Software Engineer, WSO2 Inc.
Mobile: +94 771 197 211
___
11 matches
Mail list logo