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

2017-09-17 Thread 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

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

2017-09-17 Thread 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,

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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 >

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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,

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

2017-09-17 Thread 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]

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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

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

2017-09-17 Thread 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]

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

2017-09-17 Thread 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.

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

2017-09-17 Thread 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