Re: [Dev] Edit fails giving "Unable to get Workspace" for New Application on Cloud
On Tue, Feb 10, 2015 at 2:57 PM, Fathima Dilhasha wrote: > The problem was due to a known bug in Firefox. Loading of workspace > restarts after 25% is completed. Chrome works fine. > > 26% to be exact :-) ~sanjaya > Thanks Everyone for helping. > > Regards, > Dilhasha > > *M.N.F. Dilhasha* > Software Engineering Intern | *WSO2 Lanka* > > email : > *dilha...@wso2.com *mobile : +94 77 8449321 > > On Tue, Feb 10, 2015 at 1:51 PM, Fathima Dilhasha > wrote: > >> >> >> *M.N.F. Dilhasha* >> Software Engineering Intern | *WSO2 Lanka* >> >> email : >> *dilha...@wso2.com *mobile : +94 77 8449321 >> >> On Tue, Feb 10, 2015 at 1:10 PM, Fathima Dilhasha >> wrote: >> >>> >>> >>> *M.N.F. Dilhasha* >>> Software Engineering Intern | *WSO2 Lanka* >>> >>> email : >>> *dilha...@wso2.com *mobile : +94 77 8449321 >>> >>> On Tue, Feb 10, 2015 at 1:09 PM, Fathima Dilhasha >>> wrote: >>> >>>> >>>> *M.N.F. Dilhasha* >>>> Software Engineering Intern | *WSO2 Lanka* >>>> >>>> email : >>>> *dilha...@wso2.com *mobile : +94 77 8449321 >>>> >>>> -- Forwarded message -- >>>> From: Fathima Dilhasha >>>> Date: Tue, Feb 10, 2015 at 12:24 PM >>>> Subject: [Dev] Edit fails giving "Unable to get Workspace" for New >>>> Application on Cloud >>>> To: dev-requ...@wso2.org, Sanjaya Ratnaweera , >>>> Anuruddha Premalal >>>> >>>> >>>> Hi, >>>> >>>> I tried to create a new Java Web application on cloud. But When I try >>>> to "Edit Code", it takes me through to CodeEnvy taking a very long time and >>>> finally it gives an error "Unable to Load Worspace". Screen shot attached. >>>> >>>> Tried for JAX-WS Service as well. Gives same error. >>>> >>>> Any ideas on why this happens? >>>> >>>> *M.N.F. Dilhasha* >>>> Software Engineering Intern | *WSO2 Lanka* >>>> >>>> email : >>>> *dilha...@wso2.com *mobile : +94 77 8449321 >>>> >>>> >>> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjaya Ratnaweera Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Phone: +94 773037349 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] UI Support for the SVN Based Deployment Synchronizer
On Thu, Apr 19, 2012 at 2:59 PM, Afkham Azeez wrote: > What do you mean this will make the carbon.xml based synchronizer > obsolete? You mean we won't be able to configure the server using the > carbon.xml file and will be forced to use the UI to do that? If so, -1. It > will be a huge usability issue for sysadmins. Talk to Sanjaya & see how we > do things to manage Carbon servers in production. > > Yes, we never touch UI when managing deployments. For example in Stratoslive we change configuration files and keep them in a separate location. At the deployment time we unzip a fresh pack and sync changed configurations with that. If we store those configurations in local registry we may have to login to each and every instance and change. This is not a one time change, because sometimes we delete the pack and unzip a fresh one when there are file corruptions, etc. Anyway keeping configurations in a XML file is much easier for production deployment. Thanks ~sanjaya > > On Thu, Apr 19, 2012 at 1:52 PM, Nuwan Dias wrote: > >> Hi Hiranya, >> >> Thanks for the suggestions, will increase the SVN URL field length. Yes, >> input validations have been done. >> >> Thanks, >> NuwanD. >> >> >> On Thu, Apr 19, 2012 at 1:47 PM, Hiranya Jayathilaka wrote: >> >>> Looks pretty good. Please increase the length of the SVN URL input >>> field. URL fields are usually long. I hope proper input validations are all >>> in place. >>> >>> Thanks, >>> Hiranya >>> >>> On Thu, Apr 19, 2012 at 12:18 PM, Nuwan Dias wrote: >>> >>>> Hi, >>>> >>>> I have developed a UI for the SVN based deployment synchronizer as per >>>> the task in https://wso2.org/jira/browse/ESBJAVA-893. This will make >>>> is possible to provide svn parameters for the svn based deployment >>>> synchronizer through the UI. It will however make the existing server >>>> configuration based (carbon.xml) deployment synchronizer obsolete and will >>>> be using the local registry to store and retrieve svn parameters. >>>> >>>> A screenshot of the deployment synchronizer page is attached herewith. >>>> Suggestions welcome. >>>> >>>> Thanks, >>>> -- >>>> Nuwan Dias >>>> >>>> Software Engineer - WSO2, Inc. >>>> Integration Technologies Team >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> >>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Engineer - WSO2, Inc. >>>> Integration Technologies Team >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Associate Technical Lead; >>> WSO2 Inc.; http://wso2.org >>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >> >> >> >> -- >> Nuwan Dias >> >> Software Engineer - WSO2, Inc. >> Integration Technologies Team >> email : nuw...@wso2.com >> Phone : +94 777 775 729 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* * cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjaya Ratnaweera Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we still use wso2cloud-server.sh script in Stratos Serices?
On Mon, May 7, 2012 at 6:36 PM, Afkham Azeez wrote: > wso2cloud-server.sh has production optimization stuff & also enables the > Java Security Manager. So we need the settings in that for production use. > I'm not sure whether it is used in Stratos Live. Sanjaya? > > Nope, we are using wso2server.sh written to start with nohup, adding Security Manager parameters. Thanks ~sanjaya > On Mon, May 7, 2012 at 5:43 PM, Sameera Jayasoma wrote: > >> Most of the wso2cloud-server.sh files in the stratos services contain >> invalid stuff. We need to update them if we are using, or else we can >> remove them. >> >> Thanks, >> Sameera. >> >> >> On Mon, May 7, 2012 at 2:34 PM, Sameera Jayasoma wrote: >> >>> Subject please. >>> >>> Thanks, >>> Sameera. >>> >>> -- >>> Sameera Jayasoma >>> Technical Lead >>> >>> WSO2, Inc. (http://wso2.com) >>> email: same...@wso2.com >>> blog: http://tech.jayasoma.org >>> >>> Lean . Enterprise . Middleware >>> >> >> >> >> -- >> Sameera Jayasoma >> Technical Lead >> >> WSO2, Inc. (http://wso2.com) >> email: same...@wso2.com >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* * cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > > * > * > *Lean . Enterprise . Middleware* > > -- Sanjaya Ratnaweera Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue in ./wso2server.sh restart
Hi all, When we restart a server using "./wso2ver.sh restart" It first sends the signal to kill the process looking at wso2carbon.pid and starts the server. It kills the server using "kill -term" and sometimes it takes some time to kill a process. If the server starts before earlier process gets killed it gives startup exceptions. So I have changed wso2server.sh to wait until the process gets killed before a restart. I have updated the fix in the core[1], please update if anyone keeping product specific wso2server.sh files. Thanks ~sanjaya [1] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin/wso2server.sh -- Sanjaya Ratnaweera Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Increasing open file limit in S2 EC2 image and Cartridge base images
On Mon, May 6, 2013 at 11:04 AM, Nirmal Fernando wrote: > What about doing $subject by default? > Add it to /etc/security/limits.conf. It's already recommended in docs as well. Thanks ~sanjaya [1] http://docs.wso2.org/wiki/display/ESB460/Performance+Tuning#PerformanceTuning-OS-LevelSettings > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjaya Ratnaweera Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Phone: +94 773037349 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Server startup fails when security manager is set - Stratos setup
On Tue, Jun 26, 2012 at 2:09 PM, Dinusha Senanayaka wrote: > HI, > > I am trying to setup a local Stratos setup with latest trunk packs( packs > that has merged service & product). It gives the following error and server > startup fails. After removing security manager system properties from > wso2server.sh, server get started. Any idea ? > > The wso2server.sh copied from setup script was wrong. Fixed it. Anyway most of the devs having issues since stratos setup script is not fixed for latest trunk, I'll work on that. Thanks ~sanjaya > Error occurred during initialization of VM > java.lang.ExceptionInInitializerError > at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338) > at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320) > Caused by: java.lang.IllegalArgumentException: denied.system.properties > property is not specified. > at > org.wso2.carbon.bootstrap.CarbonSecurityManager.(CarbonSecurityManager.java:44) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at java.lang.Class.newInstance0(Class.java:355) > at java.lang.Class.newInstance(Class.java:308) > at sun.misc.Launcher.(Launcher.java:80) > at sun.misc.Launcher.(Launcher.java:43) > at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338) > at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320) > > Regards, > Dinusha. > > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjaya Ratnaweera Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] "InfoCard/OpenID Sign-in " menu in G-Reg.
On Mon, Jul 2, 2012 at 5:37 AM, Samisa Abeysinghe wrote: > Sanjaya, are we deploying the latest packs to the dev cloud? > > Yes, but we are not done with it yet. Manula configured the VM environment for this setup. Chamith is in the process of changing puppet scripts to work with latest packs because of configuration changes. Thanks ~sanjaya > > On Sun, Jul 1, 2012 at 10:44 AM, Senaka Fernando wrote: > >> Hi Ajith, >> >> Is this the only remaining issue with regards to the product-service >> merging in addition to possible issues in handlers added by Stratos >> components? >> >> Thanks, >> Senaka. >> >> On Sun, Jul 1, 2012 at 8:16 AM, Dimuthu Leelarathne wrote: >> >>> Hi Ajith, >>> >>> On Sat, Jun 30, 2012 at 11:05 PM, Ajith Vitharana wrote: >>> >>>> >>>> >>>> On Fri, Jun 22, 2012 at 1:43 PM, Thilina Buddhika wrote: >>>> >>>>> This is coming from the Identity RP UI feature which are installed as >>>>> a dependency of GApp feature in Stratos. There was a discussion to remove >>>>> GApp Feature from merged products and add it during the SLive deployment. >>>>> >>>>> DimuthuL will be able to provide a more recent update on this. >>>>> >>>> >>>> Hi DimuthuL >>>> >>>> Any updates on this ? >>>> >>>> >>> Yes. As we discussed on another thread Shariq is planning to fix this >>> the next time he is running the complete build. >>> >>> thanks, >>> dimuthu >>> >>> >>>> Thanks >>>> Ajith >>>> >>>>> >>>>> Thanks, >>>>> Thilina >>>>> >>>>> On Fri, Jun 22, 2012 at 1:38 PM, Ajith Vitharana wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> Do we need to keep this feature in merged product ? >>>>>> >>>>>> Thanks >>>>>> Ajith >>>>>> >>>>>> -- >>>>>> Ajith Vitharana. >>>>>> WSO2 Inc. - http://wso2.org >>>>>> Email : aji...@wso2.com >>>>>> Mobile : +94714631794 >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thilina Buddhika >>>>> Associate Technical Lead >>>>> WSO2 Inc. ; http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>>> phone : +94 77 44 88 727 >>>>> blog : http://blog.thilinamb.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Ajith Vitharana. >>>> WSO2 Inc. - http://wso2.org >>>> Email : aji...@wso2.com >>>> Mobile : +94714631794 >>>> >>>> >>>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com >> * >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > -- Sanjaya Ratnaweera Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Improvement to Puppet modules installation instructions document
Hi all, Looking at the installation instructions in this document[1] it's written for Ubuntu 14.04. I think it's better to mention the tested operating system version somewhere in that document. Now the Ubuntu 16.04 is resealed and if we don't specifically mention the tested version people may try in Ubuntu 16.04 with this repository. Regards ~sanjaya [1] https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improvement to Puppet modules installation instructions document
Hi Pubudu, On Wed, Jun 29, 2016 at 5:48 PM, Pubudu Gunatilaka wrote: > Hi, > > Thank you for pointing out. I have now updated with tested OSs. Please do > add any missing OSs in the list. > Thank you for looking in to this. Isn't the installation instructions specific to Ubuntu? In "installing puppet -> puppet master" section commands and repositories are specific to Ubuntu 14.04. We may have to say installing in Ubuntu 14.04 or this document is created setting up for Ubuntu. These commands wont work on Redhat. Regards ~sanjaya Puppet Master > > [1] - > https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment > > Thank you! > > On Wed, Jun 29, 2016 at 3:04 PM, Sanjaya Ratnaweera > wrote: > >> Hi all, >> Looking at the installation instructions in this document[1] it's >> written for Ubuntu 14.04. I think it's better to mention the tested >> operating system version somewhere in that document. Now the Ubuntu 16.04 >> is resealed and if we don't specifically mention the tested version people >> may try in Ubuntu 16.04 with this repository. >> >> Regards >> >> ~sanjaya >> >> >> [1] >> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- Sanjaya Ratnaweera Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Phone: +94 773037349 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improvement to Puppet modules installation instructions document
I just edited the document saying installation instructions are specific to Ubuntu 14.04. Regards ~sanjaya On Wed, Jun 29, 2016 at 5:57 PM, Sanjaya Ratnaweera wrote: > Hi Pubudu, > > > On Wed, Jun 29, 2016 at 5:48 PM, Pubudu Gunatilaka > wrote: > >> Hi, >> >> Thank you for pointing out. I have now updated with tested OSs. Please do >> add any missing OSs in the list. >> > > Thank you for looking in to this. Isn't the installation instructions > specific to Ubuntu? In "installing puppet -> puppet master" section > commands and repositories are specific to Ubuntu 14.04. We may have to say > installing in Ubuntu 14.04 or this document is created setting up for > Ubuntu. These commands wont work on Redhat. > > Regards > > ~sanjaya > Puppet Master > > > >> >> [1] - >> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment >> >> Thank you! >> >> On Wed, Jun 29, 2016 at 3:04 PM, Sanjaya Ratnaweera >> wrote: >> >>> Hi all, >>> Looking at the installation instructions in this document[1] it's >>> written for Ubuntu 14.04. I think it's better to mention the tested >>> operating system version somewhere in that document. Now the Ubuntu 16.04 >>> is resealed and if we don't specifically mention the tested version people >>> may try in Ubuntu 16.04 with this repository. >>> >>> Regards >>> >>> ~sanjaya >>> >>> >>> [1] >>> https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment >>> >>> _______ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Pubudu Gunatilaka* >> Committer and PMC Member - Apache Stratos >> Software Engineer >> WSO2, Inc.: http://wso2.com >> mobile : +94774078049 <%2B94772207163> >> >> > > > -- > Sanjaya Ratnaweera > Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. > > blog: http://www.samudura.org > homepage: http://www.samudura.net > twitter: http://twitter.com/sanjayar > Phone: +94 773037349 > > Lean . Enterprise . Middleware > -- Sanjaya Ratnaweera Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Phone: +94 773037349 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configure SSO for WSO2 products using WSO2 puppet modules
Hi Pubudu, Looks great. I have a small suggestion if it make sense. Any specific reason of having "disabled: *false" *instead of "enabled: *true" *for enabling this feature :-) Regards ~sanjaya On Wed, Jun 29, 2016 at 5:28 PM, Pubudu Gunatilaka wrote: > Hi, > > I have completed setting up sso for WSO2 products using WSO2 puppet > modules. This is really helpful when you need to automate the entire > process of setting up sso for WSO2 products. Basically you need to do the > sso changes in the product as well as in the WSO2 Identity Server or any > other Identity providers. Following are the changes that needs to be done > in hiera yaml files. > > *Any WSO2 product configuration:* > > Following hiera values [1] should be set in the product hiera file to > enable sso. Configurations include enable sso, login page url, service > provider id, sso serverice url and consumer service url. > > wso2::sso_authentication: > disabled: *false* > login_page: */carbon/admin/login.jsp* > service_provider_id: *wso2esb* > sso_service_url: *https://wso2is-default:10113/samlsso > <https://wso2is-default:10113/samlsso>* > consumer_service_url: *https://wso2esb-default:10095/acs > <https://wso2esb-default:10095/acs>* > > *WSO2 IS configuration:* > > You can create service providers in WSO2 IS based on the details you have > given to each and every product. Other fully automated option is to provide > the list of products that needs to be created service providers in WSO2 IS > hiera data file as below. > > wso2::sso_product_list: > wso2esb: > assertion_consumer_service_url: *https://wso2esb-default:9443/acs > <https://wso2esb-default:9443/acs>* > default_assertion_consumer_service_url: > *https://wso2esb-default:9443/acs > <https://wso2esb-default:9443/acs>* > wso2as: > assertion_consumer_service_url: *https://wso2as-default:9443/acs > <https://wso2as-default:9443/acs>* > default_assertion_consumer_service_url: *https://wso2as-default:9443/acs > <https://wso2as-default:9443/acs>* > > This will do the following changes in WSO2 IS side. > 1. Add a new service_provider block in sso-idp-config.xml. > 2. Create a new file under > /repository/conf/identity/service-providers/ directory with the > same name of the service provider. > > The advantage of this is we can use this with docker containers. I have > tested this in Mesos. Please share your thoughts. > > [1] - > https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/common.yaml#L169 > [2] - > https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2is/5.1.0/default/default.yaml#L35 > > Thank you! > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjaya Ratnaweera Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Phone: +94 773037349 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configure SSO for WSO2 products using WSO2 puppet modules
Hi Pubudu, On Thu, Jun 30, 2016 at 12:04 AM, Pubudu Gunatilaka wrote: > Hi, > > @Imesh: As we discussed will use sso_service_providers instead of > sso_product_list. That is more meaningful. > > @Sanjaya: These hiera data will be mapped to the placeholders in > authenticators.xml [1]. If you check the puppet template we have a property > called disabled as follows. > > > True. What you have done is correct. Improvement needs to be done in configuration file :-) Regards ~sanjaya > > > So here, we cannot use as @sso_authentication['enabled'], because it will > mark the disabled property as the opposite way. > > [1] - > https://github.com/wso2/puppet-modules/blob/master/modules/wso2esb/templates/4.9.0/repository/conf/security/authenticators.xml.erb#L31 > > Thank you! > > On Wed, Jun 29, 2016 at 7:08 PM, Sanjaya Ratnaweera > wrote: > >> Hi Pubudu, >> Looks great. I have a small suggestion if it make sense. Any specific >> reason of having "disabled: *false" *instead of "enabled: *true" *for >> enabling this feature :-) >> >> Regards >> >> ~sanjaya >> >> On Wed, Jun 29, 2016 at 5:28 PM, Pubudu Gunatilaka >> wrote: >> >>> Hi, >>> >>> I have completed setting up sso for WSO2 products using WSO2 puppet >>> modules. This is really helpful when you need to automate the entire >>> process of setting up sso for WSO2 products. Basically you need to do the >>> sso changes in the product as well as in the WSO2 Identity Server or any >>> other Identity providers. Following are the changes that needs to be done >>> in hiera yaml files. >>> >>> *Any WSO2 product configuration:* >>> >>> Following hiera values [1] should be set in the product hiera file to >>> enable sso. Configurations include enable sso, login page url, service >>> provider id, sso serverice url and consumer service url. >>> >>> wso2::sso_authentication: >>> disabled: *false* >>> login_page: */carbon/admin/login.jsp* >>> service_provider_id: *wso2esb* >>> sso_service_url: *https://wso2is-default:10113/samlsso >>> <https://wso2is-default:10113/samlsso>* >>> consumer_service_url: *https://wso2esb-default:10095/acs >>> <https://wso2esb-default:10095/acs>* >>> >>> *WSO2 IS configuration:* >>> >>> You can create service providers in WSO2 IS based on the details you >>> have given to each and every product. Other fully automated option is to >>> provide the list of products that needs to be created service providers in >>> WSO2 IS hiera data file as below. >>> >>> wso2::sso_product_list: >>> wso2esb: >>> assertion_consumer_service_url: *https://wso2esb-default:9443/acs >>> <https://wso2esb-default:9443/acs>* >>> default_assertion_consumer_service_url: >>> *https://wso2esb-default:9443/acs >>> <https://wso2esb-default:9443/acs>* >>> wso2as: >>> assertion_consumer_service_url: *https://wso2as-default:9443/acs >>> <https://wso2as-default:9443/acs>* >>> default_assertion_consumer_service_url: >>> *https://wso2as-default:9443/acs >>> <https://wso2as-default:9443/acs>* >>> >>> This will do the following changes in WSO2 IS side. >>> 1. Add a new service_provider block in sso-idp-config.xml. >>> 2. Create a new file under >>> /repository/conf/identity/service-providers/ directory with the >>> same name of the service provider. >>> >>> The advantage of this is we can use this with docker containers. I have >>> tested this in Mesos. Please share your thoughts. >>> >>> [1] - >>> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/common.yaml#L169 >>> [2] - >>> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2is/5.1.0/default/default.yaml#L35 >>> >>> Thank you! >>> -- >>> *Pubudu Gunatilaka* >>> Committer and PMC Member - Apache Stratos >>> Software Engineer >>> WSO2, Inc.: http://wso2.com >>> mobile : +94774078049 <%2B94772207163> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sanjaya Ratnaweera >> Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. >> >> blog: http://www.samudura.org >> homepage: http://www.samudura.net >> twitter: http://twitter.com/sanjayar >> Phone: +94 773037349 >> >> Lean . Enterprise . Middleware >> > > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- Sanjaya Ratnaweera Associate Technical Lead; WSO2 Inc; http://www.wso2.com/. blog: http://www.samudura.org homepage: http://www.samudura.net twitter: http://twitter.com/sanjayar Phone: +94 773037349 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configure SSO for WSO2 products using WSO2 puppet modules
Hi all, On Thu, Jun 30, 2016 at 3:34 PM, Akila Ravihansa Perera wrote: > Hi Pubudu, > > It's good that we fix this from Puppet side for now. But this should > ideally be fixed in the product. Shall we create a JIRA in the relevant > project and also create another JIRA in Puppet project to keep track of > this? > > +1. I don't see any logical reason to have it that way. > Thanks. > > On Thu, Jun 30, 2016 at 3:27 PM, Pubudu Gunatilaka > wrote: > >> Hi Sanjaya, >> >> As per the suggestion we thought of doing the change in the puppet level >> to cater this requirement as it would be more cleaner for the users. >> Ideally this should be done in the configuration file. >> >> Thanks a lot Pubudu. Otherwise it'll be bit confusing to users. Regards ~sanjaya > I have done the relevant changes in [1] and [2]. >> >> [1] - >> https://github.com/wso2/puppet-modules/blob/master/modules/wso2esb/templates/4.9.0/repository/conf/security/authenticators.xml.erb#L31 >> [2] - >> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/common.yaml#L169 >> >> Thank you! >> >> On Thu, Jun 30, 2016 at 11:03 AM, Sanjaya Ratnaweera >> wrote: >> >>> Hi Pubudu, >>> >>> On Thu, Jun 30, 2016 at 12:04 AM, Pubudu Gunatilaka >>> wrote: >>> >>>> Hi, >>>> >>>> @Imesh: As we discussed will use sso_service_providers instead of >>>> sso_product_list. That is more meaningful. >>>> >>>> @Sanjaya: These hiera data will be mapped to the placeholders in >>>> authenticators.xml [1]. If you check the puppet template we have a property >>>> called disabled as follows. >>>> >>>> >>>> >>> >>> True. What you have done is correct. Improvement needs to be done in >>> configuration file :-) >>> >>> Regards >>> >>>~sanjaya >>> >>> >>> >>> >>>> >>>> >>>> So here, we cannot use as @sso_authentication['enabled'], because it >>>> will mark the disabled property as the opposite way. >>>> >>>> [1] - >>>> https://github.com/wso2/puppet-modules/blob/master/modules/wso2esb/templates/4.9.0/repository/conf/security/authenticators.xml.erb#L31 >>>> >>>> Thank you! >>>> >>>> On Wed, Jun 29, 2016 at 7:08 PM, Sanjaya Ratnaweera >>>> wrote: >>>> >>>>> Hi Pubudu, >>>>> Looks great. I have a small suggestion if it make sense. Any >>>>> specific reason of having "disabled: *false" *instead of "enabled: *true" >>>>> *for enabling this feature :-) >>>>> >>>>> Regards >>>>> >>>>> ~sanjaya >>>>> >>>>> On Wed, Jun 29, 2016 at 5:28 PM, Pubudu Gunatilaka >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have completed setting up sso for WSO2 products using WSO2 puppet >>>>>> modules. This is really helpful when you need to automate the entire >>>>>> process of setting up sso for WSO2 products. Basically you need to do the >>>>>> sso changes in the product as well as in the WSO2 Identity Server or any >>>>>> other Identity providers. Following are the changes that needs to be done >>>>>> in hiera yaml files. >>>>>> >>>>>> *Any WSO2 product configuration:* >>>>>> >>>>>> Following hiera values [1] should be set in the product hiera file to >>>>>> enable sso. Configurations include enable sso, login page url, service >>>>>> provider id, sso serverice url and consumer service url. >>>>>> >>>>>> wso2::sso_authentication: >>>>>> disabled: *false* >>>>>> login_page: */carbon/admin/login.jsp* >>>>>> service_provider_id: *wso2esb* >>>>>> sso_service_url: *https://wso2is-default:10113/samlsso >>>>>> <https://wso2is-default:10113/samlsso>* >>>>>> consumer_service_url: *https://wso2esb-default:10095/acs >>>>>> <https://wso2esb-default:10095/acs>* >>>>>> >>>>>> *WSO2 IS configuration:* >>>>>> >>>>>> You can create service providers in WSO2 IS bas
