Re: [Dev] ${ballerina.home} variable found in the netty-transports.yml config in carbon-tranposrts

[Thusitha Thilina Dayaratne]

Hi Vinod,

In addition to what Sajith mentioned, shouldn't we move all the configs to
> the deployment.yaml, according to the C5 based config model[1]? Why are we
> having a separate config for netty?

AFAIK the idea is to move all the carbon-transport related configs to the
deployment.yaml. I think we couldn't do this due to the time constraints in
previous releases.

Thanks
Thusitha

On Mon, Sep 18, 2017 at 11:15 AM, Vinod Kavinda  wrote:

> HI All,
> In addition to what Sajith mentioned, shouldn't we move all the configs to
> the deployment.yaml, according to the C5 based config model[1]? Why are we
> having a separate config for netty?
>
> [1] - https://github.com/wso2/carbon-config/blob/master/
> docs/UpdatingConfigurations.md
>
> On Mon, Sep 18, 2017 at 11:12 AM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Sajith,
>>
>> AFAIK with the redesign of carbon-transport, OSGi functionality is no
>> longer valid in transport. But IMHO we should fix this.
>>
>> Thanks
>> Thusitha
>>
>> On Mon, Sep 18, 2017 at 11:00 AM, SajithAR Ariyarathna > > wrote:
>>
>>> Hi All,
>>>
>>> I noticed $subject [1]. Any particular reason behind this?
>>>
>>> This Ballerina variable has been introduced in v4.2.3 and presents at
>>> the latest v6.0.7 too. IMO, this variable shouldn't be in the
>>> netty-transports.yml as this is not a Ballerina repo.
>>>
>>> [1] https://github.com/wso2/carbon-transports/blob/v6.0.7/fe
>>> atures/http/org.wso2.carbon.transport.http.netty.feature/res
>>> ources/conf/netty-transports.yml#L136
>>>
>>> Thanks.
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>> 
>>>
>>
>>
>>
>> --
>> Thusitha Dayaratne
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809 <+94%2071%20275%206809>
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vinod Kavinda
> Senior Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>


-- 
Thusitha Dayaratne
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ${ballerina.home} variable found in the netty-transports.yml config in carbon-tranposrts

[Vinod Kavinda]

HI All,
In addition to what Sajith mentioned, shouldn't we move all the configs to
the deployment.yaml, according to the C5 based config model[1]? Why are we
having a separate config for netty?

[1] -
https://github.com/wso2/carbon-config/blob/master/docs/UpdatingConfigurations.md

On Mon, Sep 18, 2017 at 11:12 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Sajith,
>
> AFAIK with the redesign of carbon-transport, OSGi functionality is no
> longer valid in transport. But IMHO we should fix this.
>
> Thanks
> Thusitha
>
> On Mon, Sep 18, 2017 at 11:00 AM, SajithAR Ariyarathna 
> wrote:
>
>> Hi All,
>>
>> I noticed $subject [1]. Any particular reason behind this?
>>
>> This Ballerina variable has been introduced in v4.2.3 and presents at the
>> latest v6.0.7 too. IMO, this variable shouldn't be in the
>> netty-transports.yml as this is not a Ballerina repo.
>>
>> [1] https://github.com/wso2/carbon-transports/blob/v6.0.7/fe
>> atures/http/org.wso2.carbon.transport.http.netty.feature/res
>> ources/conf/netty-transports.yml#L136
>>
>> Thanks.
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>> 
>>
>
>
>
> --
> Thusitha Dayaratne
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809 <+94%2071%20275%206809>
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ${ballerina.home} variable found in the netty-transports.yml config in carbon-tranposrts

[Thusitha Thilina Dayaratne]

Hi Sajith,

AFAIK with the redesign of carbon-transport, OSGi functionality is no
longer valid in transport. But IMHO we should fix this.

Thanks
Thusitha

On Mon, Sep 18, 2017 at 11:00 AM, SajithAR Ariyarathna 
wrote:

> Hi All,
>
> I noticed $subject [1]. Any particular reason behind this?
>
> This Ballerina variable has been introduced in v4.2.3 and presents at the
> latest v6.0.7 too. IMO, this variable shouldn't be in the
> netty-transports.yml as this is not a Ballerina repo.
>
> [1] https://github.com/wso2/carbon-transports/blob/v6.0.7/
> features/http/org.wso2.carbon.transport.http.netty.feature/
> resources/conf/netty-transports.yml#L136
>
> Thanks.
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
Thusitha Dayaratne
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ${ballerina.home} variable found in the netty-transports.yml config in carbon-tranposrts

[SajithAR Ariyarathna]

On Mon, Sep 18, 2017 at 11:00 AM, SajithAR Ariyarathna 
wrote:

> Hi All,
>
> I noticed $subject [1]. Any particular reason behind this?
>
> This Ballerina variable has been introduced in v4.2.3 and presents at the
> latest v6.0.7 too. IMO, this variable shouldn't be in the
> netty-transports.yml as this is not a Ballerina repo.
>
> [1] https://github.com/wso2/carbon-transports/blob/v6.0.7/
> features/http/org.wso2.carbon.transport.http.netty.feature/
> resources/conf/netty-transports.yml#L136
>
> Thanks.
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [C5} Inconsistent locations for runtime 'conf' directory and runtime 'deployment' directory

[Thusitha Thilina Dayaratne]

Hi Sajith,

This was done due to the assumption that users will not edit anything
inside the wso2 directory. Please refer the [1] for the detailed
explanation.

We need to do slight modification for the above directory structure. Since
> we are not allowing the end user to change any file inside wso2
> folder(ServerHome/wso2), we cannot keep the conf directory of each runtime
> inside wso2 directory. So we are planning to move out conf directory of
> each runtime from wso2 directory. Modified directory structure will look
> like below (changes from the above structure is highlighted in red colour),


[1] - [Architecture] Multiple runtime support for C5 based products

Thanks
Thusitha

On Mon, Sep 18, 2017 at 10:41 AM, SajithAR Ariyarathna 
wrote:

> Hi Platform Team,
>
> According to carbon-utils [1], runtime 'conf' directory is at
> /conf//. According to the carbon-deployment [2],
> runtime deployment directory is at /wso2//
> deployment/. I noticed an inconsistency here.
> Any particular reason behind this? IMO, runtime 'conf' directory should be
> at /wso2//conf/
>
> [1] https://github.com/wso2/carbon-utils/blob/v2.0.2/
> components/org.wso2.carbon.utils/src/main/java/org/wso2/
> carbon/utils/Utils.java#L92-L99
> [2] https://github.com/wso2/carbon-deployment/blob/v5.1.4/
> components/org.wso2.carbon.deployment.engine/src/main/
> java/org/wso2/carbon/deployment/engine/config/
> DeploymentConfiguration.java#L38
>
> Thanks.
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
Thusitha Dayaratne
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Pulasthi Mahawithana]

Hi Gayan,

On Mon, Sep 18, 2017 at 10:43 AM, Gayan Gunawardana  wrote:

>
>
> On Mon, Sep 18, 2017 at 10:19 AM, Prabath Siriwardena 
> wrote:
>
>>
>>
>> On Sun, Sep 17, 2017 at 9:42 PM, Gayan Gunawardana 
>> wrote:
>>
>>>
>>>
>>> On Mon, Sep 18, 2017 at 8:29 AM, Darshana Gunawardana >> > wrote:
>>>
 Hi Prabath,

 We do have two endpoints for SCIM 1.1 & SCIM 2. But there are some
 listeners we need to enable in order to populated relevant metadata such as
 ID, Created\Modified dates against the correct URI specified by the each
 specification.

 Given that, different clients may use different protocol of they
 already support, we should have ability to have both protocols working
 simultaneously.

>>> According to this even single client can use SCIM 1.1 and 2.0
>>> simultaneously right ?
>>> Yes so ideally it should work but in practice it will bring some
>>> complexities. We have to test use-cases like creating user with SCIM 1.1
>>> and updating with SCIM 2.0.
>>> IMO we should support only one protocol at a time but not both.
>>>
>>
>> Can we please identify those complexities...?
>>
>> We cannot terminate support for SCIM 1.1 - both have to co-exist for few
>> releases till we deprecate SCIM 1.1. If both cannot co-exist then we need
>> to review our design...
>>
> What I am suggesting is not to terminate support for SCIM 1.1 but at a
> time enable only.
> Enable SCIM 1.1 as default option. If client applications work with SCIM
> 1.1 they can continue. If client applications want to work with SCIM 2.0 we
> should be able to enable SCIM 2.0 by disabling SCIM 1.1 from
> configurations.
>

What I initially suggested was the other way around. That is having SCIM 2
as default and make SCIM 1.1 to enable with a config change. The reason is,
for any new users, they can use the newer standard OOTB without any config
changes. And for existing users who are using SCIM 1.1 clients will anyway
need to migrate to 5.4.0. During the migration, we keep the existing
configuration. So for them SCIM 1.1 will be enabled by default after the
migration process (They may switch later if needed).

Anyway, as Darshana mentioned, We'll look for the possibility of having
both of them enabled at once.

>
>> Thanks & regards,
>> -Prabath
>>
>>
>>
>>>
 Created: https://wso2.org/jira/browse/IDENTITY-6458 to track this.

 Thanks,

 On Mon, Sep 18, 2017 at 8:11 AM, Darshana Gunawardana <
 darsh...@wso2.com> wrote:

> Hi Gayan,
>
> Due to the limitation we have in the user core level, we don't support
> complex filtering, pagination, sorting. Refer [1] & [2].
>
> [1] https://github.com/wso2-extensions/identity-inbound-prov
> isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identi
> ty.scim2.common/src/main/java/org/wso2/carbon/identity/scim2
> /common/impl/SCIMUserManager.java#L834
> [2] https://github.com/wso2-extensions/identity-inbound-prov
> isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identi
> ty.scim2.common/src/main/java/org/wso2/carbon/identity/scim2
> /common/impl/SCIMUserManager.java#L793
>
> Thanks,
>
> On Mon, Sep 18, 2017 at 7:50 AM, Gayan Gunawardana 
> wrote:
>
>>
>>
>> On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
>> vindula...@cse.mrt.ac.lk> wrote:
>>
>>> Hi,
>>>
>>> +1 for this as the global adoption of SCIM 2.0 is right on the track
>>> as Ishara has mentioned.
>>>
>> @Vindula
>> Do we support pagination, complex filters and bulk operation to
>> resolve cyclic dependencies. As I know you have implemented these 
>> features
>> but there are some limitations because of C4 user core component. I am 
>> not
>> sure about the meaning of word "default" but if we are promoting SCIM 
>> 2.0,
>> have to inform what is the real value getting out of it.
>>
>>>
>>> Thanks
>>>
>>> *Vindula Jayawardana*
>>> Computer Science and Engineering Dept.
>>> University of Moratuwa
>>> mobile : +713462554
>>> Email : vindula...@cse.mrt.ac.lk
>>>
>>> 
>>> 
>>> 
>>> 
>>>
>>> *“Respect is how to treat everyone, not just those you want to
>>> impress. "*
>>>
>>>
>>> *-Richard Branson-*
>>>
>>>
>>>
>>> On 11 September 2017 at 19:10, Darshana Gunawardana <
>>> darsh...@wso2.com> wrote:
>>>
 One aspect is that we don't have a SCIM 2.0 outbound provisioning
 connector available. So IS to IS provisioning will not be smooth until 
 we
 get the outbound provisioning connector ready.

 On 

[Dev] ${ballerina.home} variable found in the netty-transports.yml config in carbon-tranposrts

[SajithAR Ariyarathna]

Hi All,

I noticed $subject [1]. Any particular reason behind this?

This Ballerina variable has been introduced in v4.2.3 and presents at the
latest v6.0.7 too. IMO, this variable shouldn't be in the
netty-transports.yml as this is not a Ballerina repo.

[1]
https://github.com/wso2/carbon-transports/blob/v6.0.7/features/http/org.wso2.carbon.transport.http.netty.feature/resources/conf/netty-transports.yml#L136

Thanks.

-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Gayan Gunawardana]

On Mon, Sep 18, 2017 at 10:19 AM, Prabath Siriwardena 
wrote:

>
>
> On Sun, Sep 17, 2017 at 9:42 PM, Gayan Gunawardana  wrote:
>
>>
>>
>> On Mon, Sep 18, 2017 at 8:29 AM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi Prabath,
>>>
>>> We do have two endpoints for SCIM 1.1 & SCIM 2. But there are some
>>> listeners we need to enable in order to populated relevant metadata such as
>>> ID, Created\Modified dates against the correct URI specified by the each
>>> specification.
>>>
>>> Given that, different clients may use different protocol of they already
>>> support, we should have ability to have both protocols working
>>> simultaneously.
>>>
>> According to this even single client can use SCIM 1.1 and 2.0
>> simultaneously right ?
>> Yes so ideally it should work but in practice it will bring some
>> complexities. We have to test use-cases like creating user with SCIM 1.1
>> and updating with SCIM 2.0.
>> IMO we should support only one protocol at a time but not both.
>>
>
> Can we please identify those complexities...?
>
> We cannot terminate support for SCIM 1.1 - both have to co-exist for few
> releases till we deprecate SCIM 1.1. If both cannot co-exist then we need
> to review our design...
>
What I am suggesting is not to terminate support for SCIM 1.1 but at a time
enable only.
Enable SCIM 1.1 as default option. If client applications work with SCIM
1.1 they can continue. If client applications want to work with SCIM 2.0 we
should be able to enable SCIM 2.0 by disabling SCIM 1.1 from
configurations.

>
> Thanks & regards,
> -Prabath
>
>
>
>>
>>> Created: https://wso2.org/jira/browse/IDENTITY-6458 to track this.
>>>
>>> Thanks,
>>>
>>> On Mon, Sep 18, 2017 at 8:11 AM, Darshana Gunawardana >> > wrote:
>>>
 Hi Gayan,

 Due to the limitation we have in the user core level, we don't support
 complex filtering, pagination, sorting. Refer [1] & [2].

 [1] https://github.com/wso2-extensions/identity-inbound-prov
 isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identi
 ty.scim2.common/src/main/java/org/wso2/carbon/identity/scim2
 /common/impl/SCIMUserManager.java#L834
 [2] https://github.com/wso2-extensions/identity-inbound-prov
 isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identi
 ty.scim2.common/src/main/java/org/wso2/carbon/identity/scim2
 /common/impl/SCIMUserManager.java#L793

 Thanks,

 On Mon, Sep 18, 2017 at 7:50 AM, Gayan Gunawardana 
 wrote:

>
>
> On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
> vindula...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> +1 for this as the global adoption of SCIM 2.0 is right on the track
>> as Ishara has mentioned.
>>
> @Vindula
> Do we support pagination, complex filters and bulk operation to
> resolve cyclic dependencies. As I know you have implemented these features
> but there are some limitations because of C4 user core component. I am not
> sure about the meaning of word "default" but if we are promoting SCIM 2.0,
> have to inform what is the real value getting out of it.
>
>>
>> Thanks
>>
>> *Vindula Jayawardana*
>> Computer Science and Engineering Dept.
>> University of Moratuwa
>> mobile : +713462554
>> Email : vindula...@cse.mrt.ac.lk
>>
>> 
>> 
>> 
>> 
>>
>> *“Respect is how to treat everyone, not just those you want to
>> impress. "*
>>
>>
>> *-Richard Branson-*
>>
>>
>>
>> On 11 September 2017 at 19:10, Darshana Gunawardana <
>> darsh...@wso2.com> wrote:
>>
>>> One aspect is that we don't have a SCIM 2.0 outbound provisioning
>>> connector available. So IS to IS provisioning will not be smooth until 
>>> we
>>> get the outbound provisioning connector ready.
>>>
>>> On Mon, Sep 11, 2017 at 5:34 PM, Pulasthi Mahawithana <
>>> pulast...@wso2.com> wrote:
>>>
 Hi,

 Shall we make $subject instead of SCIM 1.1? Any known issues on
 having it as default? Users who are migrating from older versions will
 still have SCIM 1.1 configs and won't be affected as they would keep 
 the
 old configs.


 --
 *Pulasthi Mahawithana*
 Senior Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022 <+94%2071%20517%209022>
 Blog: https://medium.com/@pulasthi7/

 

>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: 

Re: [Dev] WSO2 ESB Broker Re-Connection in case of Broker Failure

[Charini Nanayakkara]

Hi Junior,

I tried this scenario with a topic subscription but couldn't reproduce the
issue. The exact same jndi properties were used whereas the axis
configurations were same except for the fact that I tried with a topic. Not
sure whether it's specific to queues. Will test that scenario and update
you.

Thank you
Charini

On Fri, Sep 15, 2017 at 5:14 PM, Júnior  wrote:

> Hi,
>
>  I am trying to setup a connection to the WSO2 MB from the WSO2 ESB, in a
> way that in case of a Broker failure or shutdown, ESB be able to handle
> that and reconnect to it once Broker is up and running.
>
> I have this setup in axis2.xml:
>
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">conf/jndi.properties
>  locked="false">QueueConnectionFactory
>  locked="false">queue
>  locked="false">20
>  locked="false">20
>  locked="false">30
> 
>
> And in jndi.properties I have this settings for broker failover:
>
> connectionfactory.QueueConnectionFactory=amqp://admin:admin@carbon/carbon?failover='roundrobin'='2'='tcp://brk1:5675?retries='5'='50';tcp://brk2:5675?retries='5'='50''
>
> I noticed that when, we shutdown only one of the instances it handles the
> failover defined in jndi.properties, but when we shutdown both brokers and
> restart them, the proxy services that are pooling messages from the queues
> do not process any message, like the connection with the Broker were not ok.
>
> Is there any specific parameter that we need to add on axis2.xml or
> jndi.properties that could helps to achieve this requirement?
>
> Thanks in advance,
>
> https://stackoverflow.com/questions/46238761/wso2-esb-
> broker-re-connection-in-case-of-broker-failure
>
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Charini Vimansha Nanayakkara*
Software Engineer at WSO2

Mobile: 0714126293
E-mail: chari...@wso2.com
Blog: http://www.charini.me/


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [C5} Inconsistent locations for runtime 'conf' directory and runtime 'deployment' directory

[SajithAR Ariyarathna]

Hi Platform Team,

According to carbon-utils [1], runtime 'conf' directory is at
/conf//. According to the carbon-deployment [2],
runtime deployment directory is at /wso2//deployment/.
I noticed an inconsistency here.
Any particular reason behind this? IMO, runtime 'conf' directory should be
at /wso2//conf/

[1]
https://github.com/wso2/carbon-utils/blob/v2.0.2/components/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/Utils.java#L92-L99
[2]
https://github.com/wso2/carbon-deployment/blob/v5.1.4/components/org.wso2.carbon.deployment.engine/src/main/java/org/wso2/carbon/deployment/engine/config/DeploymentConfiguration.java#L38

Thanks.
-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Prabath Siriwardena]

On Sun, Sep 17, 2017 at 9:42 PM, Gayan Gunawardana  wrote:

>
>
> On Mon, Sep 18, 2017 at 8:29 AM, Darshana Gunawardana 
> wrote:
>
>> Hi Prabath,
>>
>> We do have two endpoints for SCIM 1.1 & SCIM 2. But there are some
>> listeners we need to enable in order to populated relevant metadata such as
>> ID, Created\Modified dates against the correct URI specified by the each
>> specification.
>>
>> Given that, different clients may use different protocol of they already
>> support, we should have ability to have both protocols working
>> simultaneously.
>>
> According to this even single client can use SCIM 1.1 and 2.0
> simultaneously right ?
> Yes so ideally it should work but in practice it will bring some
> complexities. We have to test use-cases like creating user with SCIM 1.1
> and updating with SCIM 2.0.
> IMO we should support only one protocol at a time but not both.
>

Can we please identify those complexities...?

We cannot terminate support for SCIM 1.1 - both have to co-exist for few
releases till we deprecate SCIM 1.1. If both cannot co-exist then we need
to review our design...

Thanks & regards,
-Prabath



>
>> Created: https://wso2.org/jira/browse/IDENTITY-6458 to track this.
>>
>> Thanks,
>>
>> On Mon, Sep 18, 2017 at 8:11 AM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi Gayan,
>>>
>>> Due to the limitation we have in the user core level, we don't support
>>> complex filtering, pagination, sorting. Refer [1] & [2].
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-prov
>>> isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identi
>>> ty.scim2.common/src/main/java/org/wso2/carbon/identity/scim2
>>> /common/impl/SCIMUserManager.java#L834
>>> [2] https://github.com/wso2-extensions/identity-inbound-prov
>>> isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identi
>>> ty.scim2.common/src/main/java/org/wso2/carbon/identity/scim2
>>> /common/impl/SCIMUserManager.java#L793
>>>
>>> Thanks,
>>>
>>> On Mon, Sep 18, 2017 at 7:50 AM, Gayan Gunawardana 
>>> wrote:
>>>


 On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
 vindula...@cse.mrt.ac.lk> wrote:

> Hi,
>
> +1 for this as the global adoption of SCIM 2.0 is right on the track
> as Ishara has mentioned.
>
 @Vindula
 Do we support pagination, complex filters and bulk operation to resolve
 cyclic dependencies. As I know you have implemented these features but
 there are some limitations because of C4 user core component. I am not sure
 about the meaning of word "default" but if we are promoting SCIM 2.0,  have
 to inform what is the real value getting out of it.

>
> Thanks
>
> *Vindula Jayawardana*
> Computer Science and Engineering Dept.
> University of Moratuwa
> mobile : +713462554
> Email : vindula...@cse.mrt.ac.lk
>
> 
> 
> 
> 
>
> *“Respect is how to treat everyone, not just those you want to
> impress. "*
>
>
> *-Richard Branson-*
>
>
>
> On 11 September 2017 at 19:10, Darshana Gunawardana  > wrote:
>
>> One aspect is that we don't have a SCIM 2.0 outbound provisioning
>> connector available. So IS to IS provisioning will not be smooth until we
>> get the outbound provisioning connector ready.
>>
>> On Mon, Sep 11, 2017 at 5:34 PM, Pulasthi Mahawithana <
>> pulast...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Shall we make $subject instead of SCIM 1.1? Any known issues on
>>> having it as default? Users who are migrating from older versions will
>>> still have SCIM 1.1 configs and won't be affected as they would keep the
>>> old configs.
>>>
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Senior Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>>> Blog: https://medium.com/@pulasthi7/
>>>
>>> 
>>>
>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Technical Lead
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>> Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Gayan Gunawardana
 Senior Software Engineer; WSO2 Inc.; http://wso2.com/
 

Re: [Dev] Dynamic client registration request fails due to no user information in the request header.

[Hasini Witharana]

+prabath

On Sat, Sep 16, 2017 at 2:08 PM, Johann Nallathamby  wrote:

>
>
> On Sat, Sep 16, 2017 at 1:37 PM, Farasath Ahamed 
> wrote:
>
>>
>>
>>
>>
>> On Sat, Sep 16, 2017 at 1:21 PM, Johann Nallathamby 
>> wrote:
>>
>>> Tenant domain of the application should always be read from the resource
>>> path - i.e. URL.
>>>
>>> We can't read it from the user since we will have to support SaaS mode,
>>> which is to authenticate with a super tenant user and create the
>>> application in a tenant.
>>>
>>
>>
>> Can we really do this? Authenticate from super tenant credentials and
>> create an application in tenant?
>>
>> Our token endpoint derives the app's tenant domain from the tenantDomain
>> of the user who created the app[1]. The assumption behind is that we can
>> create apps across tenants. ie. A user from super tenant cannot go and
>> create an app in a tenant.
>>
>
> I didn't think much about the DCR use case. I was talking in general.
> First we need to think if SaaS scenario is applicable for DCR. If it is we
> need to fix above limitation :). AFAIK above limitation comes because of
> the limitation in the schema we have. And may be some model objects.
> Nothing else. This is because OAuth2 was written way before IS 5.0.0 which
> introduced SaaS concept. May be we even don't need to fix it immediately.
> But we must follow same security pattern for all Rest endpoints, regardless
> of limitations within the component.
>
>
>>
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> /src/main/java/org/wso2/carbon/identity/oauth2/token/AccessT
>> okenIssuer.java#L129
>>
>>
>>>
>>> Please note that this is a standard pattern we follow in IS now, for
>>> almost all endpoints. Therefore no one could be ignorant about it. Any new
>>> Rest  endpoint development must follow the same security pattern. We do
>>> this with the help of the Authn/Authz valve implemented by Harsha.
>>>
>>> Regards,
>>> Johann.
>>>
>>> On Sat, Sep 16, 2017 at 1:11 PM, Hasintha Indrajee 
>>> wrote:
>>>
 Just asking for my knowledge,

 How do we identify the tenant domain of the application ? Do we have it
 in the context path ?, do we get it from user ?, or do we have anyway to
 convey it within the body (by appending to something) ? In a case if we get
 it from the identified user, how are we going to identify it from a request
 without any authentication mechanism ?.

 On Sat, Sep 16, 2017 at 12:36 PM, Gayan Gunawardana 
 wrote:

>
>
> On Fri, Sep 15, 2017 at 2:47 PM, Hasini Witharana 
> wrote:
>
>> Hi,
>>
>> In OIDC dynamic client registration, in the request header we need to
>> send an already existing user and the password to register a client in 
>> WSO2
>> Identity server.In OIDC specification[1], It is not mandatory to send 
>> user
>> details to register a client.
>>
>> When running the OIDC test suite for dynamic profile, test suite does
>> not send any user details in the header. So we can't create any client 
>> and
>> the test fails.
>>
>> For that issue if any user details are not provided in the
>> registration request we can assign an anonymous user(*wso2*.
>> *anonymous*.*user*) and register the client.
>>
> IMO correct design should be completely remove the requirement of
> having a user. If we use *"wso2*.*anonymous*.*user" *some application
> may have real username and some application may have *"wso2*.
> *anonymous*.*user" *which end up with inconsistency.
> Also need to think about creating a role per service provider if any
> user doesn't have that role.
>
>>
>> [1] - https://openid.net/specs/openid-connect-registration-1_0.html
>>
>> --
>>
>> *Hasini Witharana*
>> Software Engineering Intern | WSO2
>>
>>
>> *Email : hasi...@wso2.com *
>>
>> *Mobile : +94713850143 <+94%2071%20385%200143>[image:
>> http://wso2.com/signature] *
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "WSO2 Engineering Group" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to engineering-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout
>> .
>>
>
>
>
> --
> Gayan Gunawardana
> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>
> --
> You received this message because you are subscribed to the Google
> Groups "WSO2 Engineering Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to 

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Gayan Gunawardana]

On Mon, Sep 18, 2017 at 8:29 AM, Darshana Gunawardana 
wrote:

> Hi Prabath,
>
> We do have two endpoints for SCIM 1.1 & SCIM 2. But there are some
> listeners we need to enable in order to populated relevant metadata such as
> ID, Created\Modified dates against the correct URI specified by the each
> specification.
>
> Given that, different clients may use different protocol of they already
> support, we should have ability to have both protocols working
> simultaneously.
>
According to this even single client can use SCIM 1.1 and 2.0
simultaneously right ?
Yes so ideally it should work but in practice it will bring some
complexities. We have to test use-cases like creating user with SCIM 1.1
and updating with SCIM 2.0.
IMO we should support only one protocol at a time but not both.

>
> Created: https://wso2.org/jira/browse/IDENTITY-6458 to track this.
>
> Thanks,
>
> On Mon, Sep 18, 2017 at 8:11 AM, Darshana Gunawardana 
> wrote:
>
>> Hi Gayan,
>>
>> Due to the limitation we have in the user core level, we don't support
>> complex filtering, pagination, sorting. Refer [1] & [2].
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-prov
>> isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.ide
>> ntity.scim2.common/src/main/java/org/wso2/carbon/identity/
>> scim2/common/impl/SCIMUserManager.java#L834
>> [2] https://github.com/wso2-extensions/identity-inbound-prov
>> isioning-scim2/blob/v1.0.5/components/org.wso2.carbon.ide
>> ntity.scim2.common/src/main/java/org/wso2/carbon/identity/
>> scim2/common/impl/SCIMUserManager.java#L793
>>
>> Thanks,
>>
>> On Mon, Sep 18, 2017 at 7:50 AM, Gayan Gunawardana 
>> wrote:
>>
>>>
>>>
>>> On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
>>> vindula...@cse.mrt.ac.lk> wrote:
>>>
 Hi,

 +1 for this as the global adoption of SCIM 2.0 is right on the track as
 Ishara has mentioned.

>>> @Vindula
>>> Do we support pagination, complex filters and bulk operation to resolve
>>> cyclic dependencies. As I know you have implemented these features but
>>> there are some limitations because of C4 user core component. I am not sure
>>> about the meaning of word "default" but if we are promoting SCIM 2.0,  have
>>> to inform what is the real value getting out of it.
>>>

 Thanks

 *Vindula Jayawardana*
 Computer Science and Engineering Dept.
 University of Moratuwa
 mobile : +713462554
 Email : vindula...@cse.mrt.ac.lk

 
 
 
 

 *“Respect is how to treat everyone, not just those you want to impress.
 "*


 *-Richard Branson-*



 On 11 September 2017 at 19:10, Darshana Gunawardana 
 wrote:

> One aspect is that we don't have a SCIM 2.0 outbound provisioning
> connector available. So IS to IS provisioning will not be smooth until we
> get the outbound provisioning connector ready.
>
> On Mon, Sep 11, 2017 at 5:34 PM, Pulasthi Mahawithana <
> pulast...@wso2.com> wrote:
>
>> Hi,
>>
>> Shall we make $subject instead of SCIM 1.1? Any known issues on
>> having it as default? Users who are migrating from older versions will
>> still have SCIM 1.1 configs and won't be affected as they would keep the
>> old configs.
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: https://medium.com/@pulasthi7/
>>
>> 
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Gayan Gunawardana
>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
>>> Email: ga...@wso2.com
>>> Mobile: +94 (71) 8020933
>>>
>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Technical Lead
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>> Middleware
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Darshana Gunawardana]

Hi Prabath,

We do have two endpoints for SCIM 1.1 & SCIM 2. But there are some
listeners we need to enable in order to populated relevant metadata such as
ID, Created\Modified dates against the correct URI specified by the each
specification.

Given that, different clients may use different protocol of they already
support, we should have ability to have both protocols working
simultaneously.

Created: https://wso2.org/jira/browse/IDENTITY-6458 to track this.

Thanks,

On Mon, Sep 18, 2017 at 8:11 AM, Darshana Gunawardana 
wrote:

> Hi Gayan,
>
> Due to the limitation we have in the user core level, we don't support
> complex filtering, pagination, sorting. Refer [1] & [2].
>
> [1] https://github.com/wso2-extensions/identity-inbound-
> provisioning-scim2/blob/v1.0.5/components/org.wso2.carbon.
> identity.scim2.common/src/main/java/org/wso2/carbon/
> identity/scim2/common/impl/SCIMUserManager.java#L834
> [2] https://github.com/wso2-extensions/identity-inbound-
> provisioning-scim2/blob/v1.0.5/components/org.wso2.carbon.
> identity.scim2.common/src/main/java/org/wso2/carbon/
> identity/scim2/common/impl/SCIMUserManager.java#L793
>
> Thanks,
>
> On Mon, Sep 18, 2017 at 7:50 AM, Gayan Gunawardana  wrote:
>
>>
>>
>> On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
>> vindula...@cse.mrt.ac.lk> wrote:
>>
>>> Hi,
>>>
>>> +1 for this as the global adoption of SCIM 2.0 is right on the track as
>>> Ishara has mentioned.
>>>
>> @Vindula
>> Do we support pagination, complex filters and bulk operation to resolve
>> cyclic dependencies. As I know you have implemented these features but
>> there are some limitations because of C4 user core component. I am not sure
>> about the meaning of word "default" but if we are promoting SCIM 2.0,  have
>> to inform what is the real value getting out of it.
>>
>>>
>>> Thanks
>>>
>>> *Vindula Jayawardana*
>>> Computer Science and Engineering Dept.
>>> University of Moratuwa
>>> mobile : +713462554
>>> Email : vindula...@cse.mrt.ac.lk
>>>
>>> 
>>> 
>>> 
>>> 
>>>
>>> *“Respect is how to treat everyone, not just those you want to impress.
>>> "*
>>>
>>>
>>> *-Richard Branson-*
>>>
>>>
>>>
>>> On 11 September 2017 at 19:10, Darshana Gunawardana 
>>> wrote:
>>>
 One aspect is that we don't have a SCIM 2.0 outbound provisioning
 connector available. So IS to IS provisioning will not be smooth until we
 get the outbound provisioning connector ready.

 On Mon, Sep 11, 2017 at 5:34 PM, Pulasthi Mahawithana <
 pulast...@wso2.com> wrote:

> Hi,
>
> Shall we make $subject instead of SCIM 1.1? Any known issues on having
> it as default? Users who are migrating from older versions will still have
> SCIM 1.1 configs and won't be affected as they would keep the old configs.
>
>
> --
> *Pulasthi Mahawithana*
> Senior Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022 <+94%2071%20517%209022>
> Blog: https://medium.com/@pulasthi7/
>
> 
>



 --
 Regards,


 *Darshana Gunawardana*Technical Lead
 WSO2 Inc.; http://wso2.com

 *E-mail: darsh...@wso2.com *
 *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
 Middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Gayan Gunawardana
>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
>> Email: ga...@wso2.com
>> Mobile: +94 (71) 8020933
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>



-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Darshana Gunawardana]

Hi Gayan,

Due to the limitation we have in the user core level, we don't support
complex filtering, pagination, sorting. Refer [1] & [2].

[1]
https://github.com/wso2-extensions/identity-inbound-provisioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identity.scim2.common/src/main/java/org/wso2/carbon/identity/scim2/common/impl/SCIMUserManager.java#L834
[2]
https://github.com/wso2-extensions/identity-inbound-provisioning-scim2/blob/v1.0.5/components/org.wso2.carbon.identity.scim2.common/src/main/java/org/wso2/carbon/identity/scim2/common/impl/SCIMUserManager.java#L793

Thanks,

On Mon, Sep 18, 2017 at 7:50 AM, Gayan Gunawardana  wrote:

>
>
> On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
> vindula...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> +1 for this as the global adoption of SCIM 2.0 is right on the track as
>> Ishara has mentioned.
>>
> @Vindula
> Do we support pagination, complex filters and bulk operation to resolve
> cyclic dependencies. As I know you have implemented these features but
> there are some limitations because of C4 user core component. I am not sure
> about the meaning of word "default" but if we are promoting SCIM 2.0,  have
> to inform what is the real value getting out of it.
>
>>
>> Thanks
>>
>> *Vindula Jayawardana*
>> Computer Science and Engineering Dept.
>> University of Moratuwa
>> mobile : +713462554
>> Email : vindula...@cse.mrt.ac.lk
>>
>> 
>> 
>> 
>> 
>>
>> *“Respect is how to treat everyone, not just those you want to impress. "*
>>
>>
>> *-Richard Branson-*
>>
>>
>>
>> On 11 September 2017 at 19:10, Darshana Gunawardana 
>> wrote:
>>
>>> One aspect is that we don't have a SCIM 2.0 outbound provisioning
>>> connector available. So IS to IS provisioning will not be smooth until we
>>> get the outbound provisioning connector ready.
>>>
>>> On Mon, Sep 11, 2017 at 5:34 PM, Pulasthi Mahawithana <
>>> pulast...@wso2.com> wrote:
>>>
 Hi,

 Shall we make $subject instead of SCIM 1.1? Any known issues on having
 it as default? Users who are migrating from older versions will still have
 SCIM 1.1 configs and won't be affected as they would keep the old configs.


 --
 *Pulasthi Mahawithana*
 Senior Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022 <+94%2071%20517%209022>
 Blog: https://medium.com/@pulasthi7/

 

>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: darsh...@wso2.com *
>>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>>> Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Gayan Gunawardana
> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>



-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

[Gayan Gunawardana]

On Mon, Sep 11, 2017 at 9:14 PM, Vindula Jayawardana <
vindula...@cse.mrt.ac.lk> wrote:

> Hi,
>
> +1 for this as the global adoption of SCIM 2.0 is right on the track as
> Ishara has mentioned.
>
@Vindula
Do we support pagination, complex filters and bulk operation to resolve
cyclic dependencies. As I know you have implemented these features but
there are some limitations because of C4 user core component. I am not sure
about the meaning of word "default" but if we are promoting SCIM 2.0,  have
to inform what is the real value getting out of it.

>
> Thanks
>
> *Vindula Jayawardana*
> Computer Science and Engineering Dept.
> University of Moratuwa
> mobile : +713462554
> Email : vindula...@cse.mrt.ac.lk
>
> 
> 
> 
> 
>
> *“Respect is how to treat everyone, not just those you want to impress. "*
>
>
> *-Richard Branson-*
>
>
>
> On 11 September 2017 at 19:10, Darshana Gunawardana 
> wrote:
>
>> One aspect is that we don't have a SCIM 2.0 outbound provisioning
>> connector available. So IS to IS provisioning will not be smooth until we
>> get the outbound provisioning connector ready.
>>
>> On Mon, Sep 11, 2017 at 5:34 PM, Pulasthi Mahawithana > > wrote:
>>
>>> Hi,
>>>
>>> Shall we make $subject instead of SCIM 1.1? Any known issues on having
>>> it as default? Users who are migrating from older versions will still have
>>> SCIM 1.1 configs and won't be affected as they would keep the old configs.
>>>
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Senior Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>>> Blog: https://medium.com/@pulasthi7/
>>>
>>> 
>>>
>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Technical Lead
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>> Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Gayan Gunawardana
Senior Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IDENTITY-6405 seems to be a duplicate of IDENTITY-3966

[Nilasini Thirunavukkarasu]

Hi,

Thanks for pointing out. Seems like the fix for  IDENTITY-3966 will cover
IDENTITY-6405 scenario as well . I have updated the jira IDENTITY-3966 with
a comment.

[1 ]https://wso2.org/jira/browse/IDENTITY-3966

Thanks,
Nila

On Sat, Sep 16, 2017 at 9:02 PM, Johann Nallathamby  wrote:

> Hi Nila,
>
> IDENTITY-6405 seems to be a duplicate of IDENTITY-3966. At least they seem
> to be very much related. Therefore I have resolved as duplicate. Please
> reopen if that isn't the case.
>
> Regards,
> Johann.
>
> -- Forwarded message --
> From: Nilasini Thirunavukkarasu (JIRA) 
> Date: Mon, Sep 11, 2017 at 2:05 PM
> Subject: [Carbon-jira] [jira] (IDENTITY-6405) Could able to degrade the
> permission of the logged in user's role it makes some unexpected behaviours
> To: carbon-j...@wso2.org
>
>
> Nilasini Thirunavukkarasu
> 
> *created* an issue
>
> WSO2 Identity Server  / [image:
> Bug]  IDENTITY-6405
> 
> Could able to degrade the permission of the logged in user's role it makes
> some unexpected behaviours 
> Issue Type: [image: Bug] Bug
> Affects Versions: 5.4.0-Alpha2
> Assignee: Darshana Gunawardana
> 
> Attachments: first_window, second_window.png
> Components: user-mgt
> Created: 11/Sep/17 2:04 PM
> Fix Versions: 5.4.0-GA
> Priority: [image: Highest] Highest
> Reporter: Nilasini Thirunavukkarasu
> 
>
> 1) Add a role with all permission
> 2) Assign the role to a user (say the user as nila)
> 3) Try to logged in with nila
> 4) Update the role by un tick all the permission or keep only login
> permission
> 5) See the attachment for the output. (Attachments are added for the
> scenario "keeping only login permission")
> [image: Add Comment]
>  Add Comment
> 
>
> This message was sent by Atlassian JIRA (v7.2.2#72004-sha1:9d51328)
> [image: Atlassian logo]
>
> ___
> Carbon-jira mailing list
> carbon-j...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/carbon-jira
>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Senior Lead Solutions Engineer
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev