Re: [Dev] Supporting OpenJDK for running WSO2 products.

Hi Abimaran, AFAIK, we are supporting OpenJDK as well from C5[1] onwards. [1] - https://docs.wso2.com/display/Carbon500/Installation+Prerequisites Thanks On Sat, Jul 9, 2016 at 8:46 AM, Abimaran Kugathasan wrote: > Hi All, > > > Why we don't recommend Open JDK? > > I

Re: [Dev] Supporting OpenJDK for running WSO2 products.

Hi Abimaran, You can find a better answer in[1]. And in the comments of that post, they have pointed out some of the issues they are facing with the openJDK. [1] *http://stackoverflow.com/a/22558837 * Thanks, Chanaka. On Sat, Jul 9, 2016 at 8:46 AM,

[Dev] Supporting OpenJDK for running WSO2 products.

Hi All, Why we don't recommend Open JDK? I searched, but, couldn't find a reason for that? Is that because of any Legal/License issues? -- Thanks Abimaran Kugathasan Senior Software Engineer Email : abima...@wso2.com Mobile : +94 773922820

[Dev] [App Cloud] "When createAppInDataBase failed, adding addAppCreationEvent also getting failed"

Hi, In our app creation logic, we have number of steps and when each step failed/succeeded, we add a event to a event table. We found a situation, where the createAppInDataBase step failed, then the addAppCreationEvent also getting failed. That's because, in createAppInDataBase we add

[Dev] [VOTE] Release WSO2 MSF4J 2.0.0 RC1

Hi Devs, This is the 1st Release Candidate of WSO2 MSF4J(Microservices Framework for Java) 2.0.0. Please download, test the framework and vote. Vote will be open for 72 hours or as needed. Refer to github readmes for guides. *​Source and binary distribution files:*

[Dev] [DEV] [DAS] Navigation in Dashboards

Hi, While woring with DAS 3.1.0-SNAPSHOT I found the below irregularity. If the trailing slash is missing in the URL, page navigation in the dashboard produces a 404. 1. Create a dashboard (dashboard-1) 2. Create several pages (page-1, page-2..) 3. Navigate to the dashboard

[Dev] WSO2 App Manager 1.2.0-Beta2 Released!

*WSO2 App Manager 1.2.0-Beta2 Released!* WSO2 App Manager team is pleased to announce WSO2 App Manager 1.2.0-BETA2 release. Download distribution here . This release comes with following new features, improvements

[Dev] [Architecture] WSO2 Identity Server 5.3.0 Milestone 3 Released..!!

*WSO2 Identity Server 5.3.0 Milestone 3 Released..!!* The WSO2 Identity Server team is pleased to announce the 3rd Milestone of WSO2 Identity Server 5.3.0. You can download this distribution from https://github.com/wso2/product-is/releases/tag/v5.3.0-m3 Following list contains all features,

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

Hi Team, We identified that disabling "ValidateWhenNoSessionExists" property similar to following can resolve original session-timeout issue raised by Hasintha. org.owasp.csrfguard.ValidateWhenNoSessionExists = false Please add below lines in product "distribution" pom file to correct this

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

Thanks Jagath. We will test the fix once it's made available. Cheers, Pubudu. On Friday, 8 July 2016, Jagath Sisirakumara Ariyarathne wrote: > Hi Pubudu, > > On Fri, Jul 8, 2016 at 5:29 PM, Pubudu Priyashan

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

Hi Pubudu, On Fri, Jul 8, 2016 at 5:29 PM, Pubudu Priyashan wrote: > [+Senduran] > > We have found the same issue [1] in ESB wso2esb-5.0.0-pre-RC2.zip pack. > > [1] https://wso2.org/jira/browse/ESBJAVA-4741 > This issue has been fixed by applying required filters in property

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

On Thu, Jul 7, 2016 at 4:53 PM, Ayoma Wijethunga wrote: > Hi All, > > Original issue reported by Hasintha is relevant to how we handle session > timeout conditions with CSRFGuard filter. We are working on this and will > update with a resolution. > The reason for this behavior

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

Hi Pubudu This is only the pattern coming from kernel itself. Product level exclusions are not there in the property file. Please check with product team on this. Best Regards, Ayoma On Fri, Jul 8, 2016 at 5:59 PM, Pubudu Priyashan wrote: > Hi Ayoma, > > I had a look at " >

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

Hi Ayoma, I had a look at "repository/conf/security/Owasp.CsrfGuard.Carbon.properties" file and I can see the property [1] included in it. Can you please confirm that this is as expected? Thanks! [1] org.owasp.csrfguard.unprotected.Services=%servletContext%/services/* Cheers, Pubudu. Pubudu

Re: [Dev] Moving carbon dashboards version to 2.0.0-SNAPSHOT

Pushed the changes to master. Thanks, Tanya On Fri, Jul 8, 2016 at 5:40 PM, Dunith Dhanushka wrote: > Hi Tanya, > > Thanks for the explanation. We assume any feature that will be added later > will backward compatible. > > Regards, > Dunith > > On Fri, Jul 8, 2016 at 5:18 PM,

Re: [Dev] Persist host entry in the docker image built from a dockerfile

Hi Udara, I tried method #2 and when I checked the running container created from the built image, but the host entry was not added. Method #2 only works when I set the host entry and then use the host entry in the same line, as I have shown above. Any RUN command executed after the above RUN

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

Hi Pubudu / Senduran, This is not the exact same. "/carbon/proxyservices/" is one of EBS CSRF exclusion patterns (referring to previous filter configuration [1]). As discussed with Senduran over the call we had, this pattern needs to be added to OWASP CSRFGuard as a unprotected URL pattern ([2]

Re: [Dev] Persist host entry in the docker image built from a dockerfile

On Fri, Jul 8, 2016 at 7:49 AM, Sabra Ossen wrote: > Hi All, > > I am trying to add a host entry to /etc/hosts inside of a docker image > built from a dockerfile. An extensive search resulted in the following > results. > > 1. Add the host entry at runtime using command, >

Re: [Dev] Moving carbon dashboards version to 2.0.0-SNAPSHOT

Hi Tanya, Thanks for the explanation. We assume any feature that will be added later will backward compatible. Regards, Dunith On Fri, Jul 8, 2016 at 5:18 PM, Tanya Madurapperuma wrote: > Hi Dunith, > > All the new features were there on the 1.0.20-SNAPSHOT version. AFAIK you

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

[+Senduran] We have found the same issue [1] in ESB wso2esb-5.0.0-pre-RC2.zip pack. [1] https://wso2.org/jira/browse/ESBJAVA-4741 Pubudu D.P Senior Software Engineer - QA Team | WSO2 inc. Mobile : +94775464547 Linkedin: https://uk.linkedin.com/in/pubududp Medium: https://medium.com/@pubududp

[Dev] Persist host entry in the docker image built from a dockerfile

Hi All, I am trying to add a host entry to /etc/hosts inside of a docker image built from a dockerfile. An extensive search resulted in the following results. 1. Add the host entry at runtime using command, *docker run -it --add-host myhost:192.168.18.2 /bin/bash* This method only makes

Re: [Dev] Moving carbon dashboards version to 2.0.0-SNAPSHOT

Hi Dunith, All the new features were there on the 1.0.20-SNAPSHOT version. AFAIK you have already verified your build with 1.0.20-SNAPSHOT. Hence this will just be a version change for you. Let us know if you have any concerns. Thanks, Tanya On Fri, Jul 8, 2016 at 5:13 PM, Dunith Dhanushka

Re: [Dev] Moving carbon dashboards version to 2.0.0-SNAPSHOT

Hi Tanya, On second thought, can you be specific on new features? Since we are on the verge of DAS 3.1.0 release today, it's better to go without new features. Can you merge 4.4.7 related security fixes to 1.0.20-SNAPSHOT ? Thanks, Dunith On Fri, Jul 8, 2016 at 4:59 PM, Dunith Dhanushka

Re: [Dev] [DAS 310] Changing the logo of the dashboard

Thanks Jerad for the explanation and the links. Will follow this. Regards, Sachith On Thu, Jul 7, 2016 at 11:49 PM, Jerad Rutnam wrote: > Hi Sachith, > > Basically you have to overwrite the " > *repository\deployment\server\jaggeryapps\portal\theme\templates\dashboard.jag*" >

Re: [Dev] Moving carbon dashboards version to 2.0.0-SNAPSHOT

Ack! On Fri, Jul 8, 2016 at 4:56 PM, Tanya Madurapperuma wrote: > Hi all, > > We will be $ Subject from 1.0.20-SNAPSHOT. Reason is we have new features > added and also upgraded the carbon kernel version to 4.4.7. > > Please note this if you are pointing to carbon dashboards

Re: [Dev] [ES]Error when Importing Users in Bulk through management console

Hi Sherene, Shall we add this to IS docs. We can include the structure of the csv in [1]. [1] - https://docs.wso2.com/display/IS510/Configuring+Users#ConfiguringUsers-Importingusers Thanks, Omindu. On Fri, Jul 8, 2016 at 11:57 AM, Kasun Thennakoon wrote: > Hi Dilini, > >

[Dev] Moving carbon dashboards version to 2.0.0-SNAPSHOT

Hi all, We will be $ Subject from 1.0.20-SNAPSHOT. Reason is we have new features added and also upgraded the carbon kernel version to 4.4.7. Please note this if you are pointing to carbon dashboards 1.0.20-SNAPSHOT in any of your repos atm. Thanks, Tanya -- Tanya Madurapperuma Senior

Re: [Dev] Puppet Modules main version should be a constant

Thanks Imesh! On Fri, Jul 8, 2016 at 2:39 PM, Imesh Gunaratne wrote: > Hi Isuru, > > We fixed this in the following commit: > > https://github.com/wso2/puppet-modules/commit/6129cfe3353ae41fdd6ffd746dd7fcc0471cbf5f > > Thanks > > On Fri, Jul 8, 2016 at 2:13 PM, Imesh Gunaratne

Re: [Dev] Kernel upgrade of DS fails with jaggery extensions 1.5.3-SNAPHOT

Verified with CEP build. Thanks, Chandana and team! On Fri, Jul 8, 2016 at 2:10 PM, Tanya Madurapperuma wrote: > This is fixed with [1] in jaggery-extensions. Verified in DS build. Thanks > Chanadana ! > > [1] >

Re: [Dev] Puppet Modules main version should be a constant

Hi Isuru, We fixed this in the following commit: https://github.com/wso2/puppet-modules/commit/6129cfe3353ae41fdd6ffd746dd7fcc0471cbf5f Thanks On Fri, Jul 8, 2016 at 2:13 PM, Imesh Gunaratne wrote: > Thanks Isuru! Will fix this. > > On Fri, Jul 8, 2016 at 2:02 PM, Isuru Perera

Re: [Dev] Puppet Modules main version should be a constant

Thanks Isuru! Will fix this. On Fri, Jul 8, 2016 at 2:02 PM, Isuru Perera wrote: > I see following error when building puppet-modules [1]. Shall we fix it > properly? > > wso2-git/puppet-modules$ mci > [INFO] Scanning for projects... > [WARNING] > [WARNING] Some problems were

Re: [Dev] Kernel upgrade of DS fails with jaggery extensions 1.5.3-SNAPHOT

This is fixed with [1] in jaggery-extensions. Verified in DS build. Thanks Chanadana ! [1] https://github.com/wso2/jaggery-extensions/commit/be46b7e8966d83fdac08837c032a10121ad339ec Thanks, Tanya On Fri, Jul 8, 2016 at 9:44 AM, Tanya Madurapperuma wrote: > Hi Greg team, > > In

[Dev] Puppet Modules main version should be a constant

I see following error when building puppet-modules [1]. Shall we fix it properly? wso2-git/puppet-modules$ mci [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.wso2.puppet:wso2base-puppet-module:pom:2.0.0 [WARNING]

Re: [Dev] Regarding APPM-1160

Agree with Ruwan's point that we should not keep credentials per tenant. But, passing tenantId as a query parameter to API seems a security concern. This provides capability to access some other tenant's device list to any of the tenant having valid access token. One way that I could think of to

Re: [Dev] Regarding APPM-1160

Hi All, I think REST connector should have single endpoint. The rest call can have tenant ID in a header or as a request parameter. Then the API gateway( API-Manager) should be able to distinguish the respective endpoint if necessary. This is a functionality of APIM. The reasons are, 1. REST

Re: [Dev] [ES]Error when Importing Users in Bulk through management console

Hi Dilini, Thanks for the help,It works with a slight change to the *names_2.csv* file attached in the JIRA[1].As you suggested , I had to add a new column with the password for the user in between username and claim URL columns. Sample format of the csv file. UserName,Password,Claims >

[Dev] carbon-deployment 4.7.0 released

HI all, Please note $subject, org.wso2.carbon.deployment carbon-deployment 4.7.0 -- Best Regards, Kalpa Welivitigoda Senior Software Engineer, WSO2 Inc. http://wso2.com Email: kal...@wso2.com Mobile: +94776509215 ___ Dev mailing list Dev@wso2.org

Re: [Dev] Regarding APPM-1160

Hi Sajith, We could not keep each and every tenant authentication configuration in app-manager.xml, due to dynamic nature of tenant creation and the growth. appmgt.mdm.rest.connector is the default connector that we provided to connect with WSO2EMM. We could keep it's configurations in the