Re: [Dev] WSO2 IS 5.3.0 Cluster
Hi Praveen, Hazelcast clustering is a must for cache invalidation message propagation in WSO2 Identity Server v5.3.0. Currently, WSO2 recommends using Kubernetes as a container orchestration system in production grade WSO2 product deployments. WSO2 provides official Kubernetes resources for all its products. WSO2 provides a Kubernetes Membership Scheme for Hazelcast clustering, which is used for member discovery. At present, WSO2 does not provide Docker Swarm resources for WSO2 products. An effort to provide resources required for WSO2 product deployment on Docker Swarm involves, 1. Implementation of Docker Swarm resource definitions for WSO2 product deployments 2. A Hazelcast cluster membership scheme for cluster member discovery of WSO2 products when deployed in a Docker Swarm environment Since, WSO2 already provides the required resources for product deployments in a Kubernetes environment, can you please specify your concerns with regards to using Kubernetes as a container orchestration platform? On Tue, May 28, 2019 at 1:08 PM Praveen Kumar K S wrote: > Hello Team, > > I'm running WSO2 IS 5.3.0 as cluster using docker swarm. In my approach, > I'm adding the hostname of docker containers to hastlecast clustering > members in axis2.xml. > > I would like to know, what are the implications/challenges if I don't add > members in haslecast clustering and simply scale WSO2. > > Apparently, there is less documentation regarding WSO2 IS cluster > deployment using dockers. Please advise. > > Regards, > Praveen Kumar K S > +91-9986855625 > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Nginx dynamic config for wso2 identity server
Hi Praveen, Currently, WSO2 recommends using Kubernetes as a container orchestration system in production grade WSO2 product deployments. WSO2 provides official Kubernetes resources for all its products. In Kubernetes based deployments of WSO2 products, we recommend using the NGINX Kubernetes Ingress Controller [1]. The NGINX Kubernetes Ingress Controller provides out of the box support for dynamic generation of NGINX configuration in container based deployments. [1]: https://github.com/kubernetes/ingress-nginx On Mon, May 6, 2019 at 1:17 PM Praveen Kumar K S wrote: > Hello Team, > > I'm running wso2 cluster using dockers. But when I scale wso2 services, > how can I change nginx configuration dynamically so that nginx perform > round robin on all wso2 containers. Please advise. > > Regards, > Praveen > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Product Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of Docker and Docker Compose resources for WSO2 products. *Docker* Released artifacts: - WSO2 API Manager v2.6.0.2 - https://github.com/wso2/docker-apim/releases/tag/v2.6.0.2 - WSO2 Enterprise Integrator v6.4.0.2 - https://github.com/wso2/docker-ei/releases/tag/v6.4.0.2 - WSO2 Identity Server v5.7.0.2 - https://github.com/wso2/docker-is/releases/tag/v5.7.0.2 - WSO2 Stream Processor v4.3.0.2 - https://github.com/wso2/docker-sp/releases/tag/v4.3.0.2 Issues: - WSO2 API Manager - https://github.com/wso2/docker-apim/issues - WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/issues - WSO2 Identity Server - https://github.com/wso2/docker-is/issues - WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 product Docker and Docker Compose resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Announce] [Architecture] WSO2 Product Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of Docker and Docker Compose resources for WSO2 products. *Docker* Released artifacts: - WSO2 API Manager v2.6.0.2 - https://github.com/wso2/docker-apim/releases/tag/v2.6.0.2 - WSO2 Enterprise Integrator v6.4.0.2 - https://github.com/wso2/docker-ei/releases/tag/v6.4.0.2 - WSO2 Identity Server v5.7.0.2 - https://github.com/wso2/docker-is/releases/tag/v5.7.0.2 - WSO2 Stream Processor v4.3.0.2 - https://github.com/wso2/docker-sp/releases/tag/v4.3.0.2 Issues: - WSO2 API Manager - https://github.com/wso2/docker-apim/issues - WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/issues - WSO2 Identity Server - https://github.com/wso2/docker-is/issues - WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 product Docker and Docker Compose resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Announce] [Architecture] WSO2 Product Installation Resources Released!!!
>>>> >>>> >>>> Issues: >>>> >>>>- >>>> >>>>WSO2 API Manager - https://github.com/wso2/docker-apim/issues >>>>- >>>> >>>>WSO2 Identity Server - https://github.com/wso2/docker-is/issues >>>>- >>>> >>>>WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues >>>>- >>>> >>>>WSO2 Enterprise Integrator - >>>>https://github.com/wso2/docker-ei/issues >>>> >>>> Kubernetes >>>> >>>> Related artifacts: >>>> >>>>- >>>> >>>>WSO2 API Manager v2.6.0.1 - >>>>https://github.com/wso2/kubernetes-apim/releases/tag/v2.6.0.1 >>>>- >>>> >>>>WSO2 Identity Server v5.7.0 - >>>>https://github.com/wso2/kubernetes-is/releases/tag/v5.7.0.1 >>>>- >>>> >>>>WSO2 Stream Processor v4.3.0 - >>>>https://github.com/wso2/kubernetes-sp/releases/tag/v4.3.0.1 >>>>- >>>> >>>>WSO2 Enterprise Integrator v6.4.0 - >>>>https://github.com/wso2/kubernetes-ei/releases/tag/v6.4.0.1 >>>> >>>> >>>> Issues: >>>> >>>>- >>>> >>>>WSO2 API Manager - https://github.com/wso2/kubernetes-apim/issues >>>>- >>>> >>>>WSO2 Identity Server - https://github.com/wso2/kubernetes-is/issues >>>>- >>>> >>>>WSO2 Stream Processor - https://github.com/wso2/kubernetes-sp/issues >>>>- >>>> >>>>WSO2 Enterprise Integrator - >>>>https://github.com/wso2/kubernetes-ei/issues >>>> >>>> Puppet >>>> >>>> Related artifacts: >>>> >>>>- >>>> >>>>WSO2 API Manager v2.6.0.1 - >>>>https://github.com/wso2/puppet-apim/releases/tag/v2.6.0.1 >>>>- >>>> >>>>WSO2 Identity Server v5.7.0 - >>>>https://github.com/wso2/puppet-is/releases/tag/v5.7.0.1 >>>>- >>>> >>>>WSO2 Stream Processor v4.3.0 - >>>>https://github.com/wso2/puppet-sp/releases/tag/v4.3.0.1 >>>>- >>>> >>>>WSO2 Enterprise Integrator v6.4.0 - >>>>https://github.com/wso2/puppet-ei/releases/tag/v6.4.0.1 >>>> >>>> >>>> Issues: >>>> >>>>- >>>> >>>>WSO2 API Manager - https://github.com/wso2/puppet-apim/issues >>>>- >>>> >>>>WSO2 Identity Server - https://github.com/wso2/puppet-is/issues >>>>- >>>> >>>>WSO2 Stream Processor - https://github.com/wso2/puppet-sp/issues >>>>- >>>> >>>>WSO2 Enterprise Integrator - >>>>https://github.com/wso2/puppet-ei/issues >>>> >>>> Vagrant >>>> >>>> Related artifacts: >>>> >>>>- >>>> >>>>WSO2 API Manager v2.6.0.1 - >>>>https://github.com/wso2/vagrant-apim/releases/tag/v2.6.0.1 >>>>- >>>> >>>>WSO2 Identity Server v5.7.0 - >>>>https://github.com/wso2/vagrant-is/releases/tag/v5.7.0.1 >>>>- >>>> >>>>WSO2 Stream Processor v4.3.0 - >>>>https://github.com/wso2/vagrant-sp/releases/tag/v4.3.0.1 >>>>- >>>> >>>>WSO2 Enterprise Integrator v6.4.0 - >>>>https://github.com/wso2/vagrant-ei/releases/tag/v6.4.0.1 >>>> >>>> >>>> Issues: >>>> >>>>- >>>> >>>>WSO2 API Manager - https://github.com/wso2/vagrant-apim/issues >>>>- >>>> >>>>WSO2 Identity Server - https://github.com/wso2/vagrant-is/issues >>>>- >>>> >>>>WSO2 Stream Processor - https://github.com/wso2/vagrant-sp/issues >>>>- >>>> >>>>WSO2 Enterprise Integrator - >>>>https://github.com/wso2/vagrant-ei/issues >>>> >>>> >>>> How You Can Contribute >>>> >>>> Join our mailing list and correspond with the developers directly. >>>> >>>> Developer List: dev@wso2.org >>>> >>>> User List: u...@wso2.org >>>> >>>> Reporting Issues >>>> >>>> We encourage you to report issues and documentation faults regarding >>>> WSO2 Ansible, AWS, Docker, Kubernetes, Puppet and Vagrant resource >>>> through respective repositories by creating issues. >>>> >>>> Thank you! >>>> >>>> WSO2 Installation Experience Team >>>> >>>> Vimukthi Perera >>>> Software Engineer >>>> WSO2 Inc. >>>> >>>> Mobile: +94771153999 >>>> Blog: https://medium.com/@vimukthiperera >>>> Web: http://wso2.com >>>> >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> ___ >>>> Architecture mailing list >>>> architect...@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> >>> >>> -- >>> *Nuwan Dias* | Director | WSO2 Inc. >>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>> [image: Signature.jpg] >>> ___ >>> Announce mailing list >>> annou...@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce >>> >> > > -- > *Nuwan Dias* | Director | WSO2 Inc. > (m) +94 777 775 729 | (e) nuw...@wso2.com > [image: Signature.jpg] > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Nginx Controller in K8s APIM repository
Hi Isuru, adding the NGINX Ingress Controller is included as a step in readme documentation, as @Chiran has mentioned [1]. This has been done since the existing resources in 2.1.x branch did not work out successfully when deployed in Kubernetes environments where Role-Based Access Control has been enabled by default [2]. The NGINX Ingress Controller Installation Guide [3] provides instructions on deploying this in different environments. [1]: https://github.com/wso2/kubernetes-apim/tree/master/pattern-1#9-deploy-kubernetes-ingress-resource [2]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/ [3]: https://kubernetes.github.io/ingress-nginx/deploy/ On Fri, Jul 27, 2018 at 11:03 AM Isuru Haththotuwa wrote: > I could not find $subject in the master branch [1]. But its there in the > 2.1.x branch. Any reason to remove this from the master branch? > > [1]. > https://github.com/wso2/kubernetes-apim/tree/master/pattern-1/ingresses > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Product Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of Docker and Kubernetes resources for WSO2 products. *Docker* Released artifacts: - WSO2 Stream Processor v4.1.0.3 - https://github.com/wso2/docker-sp/releases/tag/v4.1.0.3 Issues: - WSO2 Stream Processor - https://github.com/wso2/docker-sp/issues *Kubernetes* Released artifacts: - WSO2 API Manager v2.2.0.1 - https://github.com/wso2/kubernetes-apim/releases/tag/v2.2.0.1 - WSO2 Stream Processor v4.1.0.1 - https://github.com/wso2/kubernetes-sp/releases/tag/4.1.0.1 Issues: - WSO2 API Manager - https://github.com/wso2/kubernetes-apim/issues - WSO2 Stream Processor - https://github.com/wso2/kubernetes-sp/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 Docker and Kubernetes resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Product Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of Docker and Kubernetes resources for WSO2 products. *Docker* Released artifacts: - WSO2 API Manager v2.2.0.3 - https://github.com/wso2/docker-apim/releases/tag/v2.2.0.3 - WSO2 Enterprise Integrator v6.2.0.6 - https://github.com/wso2/docker-ei/releases/tag/v6.2.0.6 - WSO2 Identity Server v5.5.0.4 - https://github.com/wso2/docker-is/releases/tag/v5.5.0.4 Issues: - WSO2 API Manager - https://github.com/wso2/docker-apim/issues - WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/issues - WSO2 Identity Server - https://github.com/wso2/docker-is/issues *Kubernetes* Released artifacts: - WSO2 Enterprise Integrator v6.2.0.9 - https://github.com/wso2/kubernetes-ei/releases/tag/v6.2.0.9 - WSO2 Identity Server v5.5.0.4 - https://github.com/wso2/kubernetes-is/releases/tag/v5.5.0.4 Issues: - WSO2 Enterprise Integrator - https://github.com/wso2/kubernetes-ei/issues - WSO2 Identity Server - https://github.com/wso2/kubernetes-is/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 Docker and Kubernetes resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Product Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of AWS, Docker and Kubernetes resources for WSO2 products. *AWS* Released artifacts: - WSO2 Enterprise Integrator v6.2.0.1 - https://github.com/wso2/aws-ei/releases/tag/v6.2.0.1 - WSO2 Stream Processor v4.1.0.1 - https://github.com/wso2/aws-sp/releases/tag/v4.1.0.1 Issues: - WSO2 Enterprise Integrator - https://github.com/wso2/aws-ei/issues - WSO2 Stream Processor - https://github.com/wso2/aws-sp/issues *Docker* Released artifacts: - WSO2 Identity Server v5.5.0.3 - https://github.com/wso2/docker-is/releases/tag/v5.5.0.3 Issues: - WSO2 Identity Server - https://github.com/wso2/docker-is/issues *Kubernetes* Released artifacts: - WSO2 Identity Server v5.5.0.3 - https://github.com/wso2/kubernetes-is/releases/tag/v5.5.0.3 Issues: - WSO2 Identity Server - https://github.com/wso2/kubernetes-is/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 AWS, Docker and Kubernetes resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] `java.sql.SQLException: Subquery returns more than 1 row` in a clustered deployment of WSO2 Enterprise Integrator
Hi all, I am currently working on building Kubernetes resources for WSO2 products. During the process of building Kubernetes resources for WSO2 Enterprise Integrator, I've been experiencing the $subject error, intermittently during server startup. It was mostly experienced when attempting to start two profile nodes (e.g. two Integrator profile pods), in parallel. I've already created an issue in the product repository under which the complete set of server startup logs (including the error logs) have been provided [1]. Any help and suggestions are highly appreciated. [1]: https://github.com/wso2/product-ei/issues/2235 -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] HTTP 504 Gateway Timeout error when attempting to access the WSO2 Identity Server Analytics Dashboard portal
Hi all,
I am currently working on building Kubernetes resources for WSO2 products.
During the process of building Kubernetes resources for WSO2 Identity
Server's deployment pattern 2, I experienced the following HTTP 504 Gateway
Timeout error when attempting to access the WSO2 Identity Server Analytics
Dashboard.
*[2018-06-09 17:45:56,095] INFO
{org.apache.shindig.gadgets.http.BasicHttpFetcher} -
https://wso2is-analytics/shindig/rpc?method=system.listMethods&st=-1:-1:0:*:0:0:default:1528566365
<https://wso2is-analytics/shindig/rpc?method=system.listMethods&st=-1:-1:0:*:0:0:default:1528566365>
has timed out because of the following exception:
org.apache.shindig.gadgets.http.BasicHttpFetcher - wso2is-analytics: Name
or service not known - 177 ms.*
*[2018-06-09 17:45:56,276] ERROR
{org.apache.shindig.gadgets.render.DefaultServiceFetcher} - An HTTP 504
error occurred when fetching service methods from the
https://wso2is-analytics/shindig/rpc <https://wso2is-analytics/shindig/rpc>
endpoint.*
According to [1], this occurs when shindig attempts to load Google
Analytics APIs and is deemed to be fixed in the past.
As per the logs, it is clear that the host name `*wso2is-analytics*` I have
provided under the Kubernetes Ingress resource is not resolvable. Based on
[2], I tried editing the shindig.host (with `*wso2is-analytics`*) and
shindig.port (with port 443) properties in the
*/repository/deployment/server/webapps/shindig/WEB-INF/web.xml*
file.
But it was not successful.
How can I fix this issue? Any help and suggestions are highly appreciated.
[1]: [Dev] Shindig error on DS portal startup, due to connectivity errors
to google
[2]:
https://docs.wso2.com/display/IS550/Setting+Up+Deployment+Pattern+2#SettingUpDeploymentPattern2-Settingupthedashboard
--
Yours sincerely,
*Chiranga Alwis*
Software Engineer | WSO2
*Mobile : *+94775930497
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
*Medium:* https://medium.com/@chirangaalwis
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] WSO2 Product Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of AWS and Kubernetes resources for WSO2 products. *AWS* Released Artifacts: - WSO2 API Manager v2.2.0.2: https://github.com/wso2/aws-apim/releases/tag/v2.2.0.2 Issues: - WSO2 API Manager v2.2.0.2: https://github.com/wso2/aws-apim/issues *Kubernetes* Released Artifacts: - WSO2 Enterprise Integrator v6.2.0.5: https://github.com/wso2/kubernetes-ei/releases/tag/v6.2.0.5 Issues: - WSO2 Enterprise Integrator v6.2.0.5: https://github.com/wso2/kubernetes-ei/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 AWS and Kubernetes resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Installation Resources Released!
WSO2 Installation Experience team is pleased to announce the release of WSO2 Docker, Vagrant and Kubernetes resources for WSO2 products. *Docker* Released Artifacts: - WSO2 Enterprise Integrator v6.2.0.2 - https://github.com/wso2/docker-ei/releases/tag/v6.2.0.2 - WSO2 API Manager v2.2.0.2 - https://github.com/wso2/docker-apim/releases/tag/v2.2.0.2 - WSO2 Identity Server v5.5.0.2 - https://github.com/wso2/docker-is/releases/tag/v5.5.0.2 - WSO2 Stream Processor v4.1.0.2 - https://github.com/wso2/docker-sp/releases/tag/v4.1.0.2 - WSO2 IoT Server v3.3.0.2 - https://github.com/wso2/docker-iot/releases/tag/v3.3.0.2 Issues: - WSO2 Enterprise Integrator v6.2.0.2 - https:// github.com/wso2/docker-ei/issues <https://github.com/wso2/docker-ei/issues> - WSO2 API Manager v2.2.0.2 - https://github.com/wso2/docker-apim/issues - WSO2 Identity Server v5.5.0.2 - https://github.com/wso2/docker-is/ issues - WSO2 Stream Processor v4.1.0.2 - https://github.com/wso2/docker-sp/ issues - WSO2 IoT Server v3.3.0.2 - https://github.com/wso2/docker-iot/issues *Vagrant* Released Artifacts: - WSO2 API Manager v2.2.0.2 - *https://github.com/wso2/vagrant-apim/releases/tag/v2.2.0.2 <https://github.com/wso2/vagrant-apim/releases/tag/v2.2.0.2>* Issues: - WSO2 API Manager v2.2.0.2 - https://github.com/wso2/vagrant-apim/issues *Kubernetes* Released Artifacts: - WSO2 Enterprise Integrator v6.2.0.2 - https://github.com/wso2/ kubernetes-ei/releases/tag/v6.2.0.2 <https://github.com/wso2/kubernetes-ei/releases/tag/v6.2.0.2> Issues: - WSO2 Enterprise Integrator v6.2.0.2 - https:// github.com/wso2/kubernetes-ei/issues <https://github.com/wso2/kubernetes-ei/issues> *How You Can Contribute* Join our mailing list and correspond with the developers directly. Developer List: dev@wso2.org User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 Docker, Vagrant and Kubernetes resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Enterprise Integrator Kubernetes Resources v6.2.0.1 Released!
WSO2 Installation Experience team is pleased to announce the initial release of WSO2 Kubernetes resources for WSO2 Enterprise Integrator 6.2.0. *Features* 1. Deployment controller for WSO2 Enterprise Integrator's Integrator profile, to easily manage corresponding pods. 2. MySQL Deployment controller for database access to test out an out-of-the-box scalable deployment. 3. Service level separation for mediation gateway and management console access to optimize request load. 4. NGINX Ingress controller to publicly expose Integration services easily. 5. Configmaps in managing pattern specific configurations to simplify rolling out of updates. 6. Dockerfiles for building required base images from the scratch. 7. Helper scripts for deploying and undeploying pattern-1 in one go. *Fixed issues* - Migrate Kubernetes resource implementations from version 6.1.1 to version 6.2.x <https://github.com/wso2/kubernetes-ei/issues/26> - Remove custom MySQL Docker image build implementation <https://github.com/wso2/kubernetes-ei/issues/28> - Remove existing Kubernetes resource deployment management scripts <https://github.com/wso2/kubernetes-ei/issues/29> - Refine Docker resources for Integrator profile <https://github.com/wso2/kubernetes-ei/issues/41> - Refine Docker resources for Analytics profile <https://github.com/wso2/kubernetes-ei/issues/42> *Supported Versions* - Kubernetes: v1.6.0 or later - Docker: v17.09.0 or later *How You Can Contribute* Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org - User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 Kubernetes resources for WSO2 Enterprise Integrator 6.2.0 by creating issues <https://github.com/wso2/kubernetes-ei/issues/new>. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pre-populate dynamically provisioned Kubernetes persistent storage
Hi Imesh/Pubudu, as per your suggestions, I've built up a preliminary version of the Docker images which make use of Kubernetes ConfigMaps for providing configuration files. Please find the relevant pull request from [1]. Plus, please see [2] for a Significant Interest Group (SIG) forum discussion I have initiated on this matter and on the possibility of using Kubernetes persistent volumes for mounting configuration files. And please check [3] for the feature request I've made for building a Kubernetes ConfigMap from a folder, recursively. You may track the progress of this feature in Kubernetes from [3]. Please feel free to share your suggestions and concerns in above discussions. [1]: https://github.com/wso2/kubernetes-ei/pull/27 [2]: https://groups.google.com/forum/#!topic/kubernetes-sig-storage/qhd2HFd7nbg [3]: https://github.com/kubernetes/kubernetes/issues/62421 On Thu, Apr 12, 2018 at 12:23 AM, Imesh Gunaratne wrote: > Hi Chiranga, > > I agree with Pubudu on using ConfigMaps for providing configuration files. > > On Tue, Apr 10, 2018 at 8:18 AM, Chiranga Alwis wrote: > >> ... >> >> But how can we pre-populate the dynamically provisioned persistent volume >> with the files with configuration changes? >> > > This would be possible with static PVs but might be difficult to handle > with dynamic PVs. > > If the user is using static PVs instructions can be provided to copy the > required files to the PVs before starting the pods. If dynamic PVs are > used PVCs might need to be deployed once for making the connection between > the PV and PVCs and then do the same. > > Thanks > Imesh > >> >> >> Your help, suggestions and concerns on this matter are highly appreciated. >> >> *Note*: Please find this [6] forum discussion I've initiated at >> Kubernetes Storage Special Interest Group [7]. >> >> [1]: https://github.com/wso2/kubernetes-ei >> [2]: Mail thread with subject "[Architecture] [Deployment] [Containers] >> An update to WSO2 product Dockerfile generalization" >> [3]: https://kubernetes-v1-4.github.io/docs/user-guide/configmap/ >> [4]: https://groups.google.com/forum/#!topic/kubernetes-users/h_FRSr5wW00 >> [5]: https://kubernetes.io/blog/2017/03/dynamic-provisioning-and- >> storage-classes-kubernetes >> [6]: https://groups.google.com/forum/#!topic/kubernetes-sig-stora >> ge/qhd2HFd7nbg >> [7]: https://github.com/kubernetes/community/tree/master/sig-storage >> >> -- >> Yours sincerely, >> >> *Chiranga Alwis* >> Software Engineer | WSO2 >> >> *Mobile : *+94775930497 >> *Email: *chirangaal...@gmail.com >> *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 >> *Medium:* https://medium.com/@chirangaalwis >> >> <http://wso2.com/signature> >> >> _______ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Imesh Gunaratne* > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Pre-populate dynamically provisioned Kubernetes persistent storage
Hi all, currently, I'm working on building Kubernetes resources for WSO2 Enterprise Integrator [1]. During this effort, I am attempting to utilize platform independent WSO2 product Docker images [2] when deploying artifacts on Kubernetes platform. Here, we are required to pass on the set of files with configuration changes to the default Docker image file system, into a pod in order to make them available at the container startup. The most straightforward solution provided by Kubernetes platform for this purpose is using ConfigMaps [3]. But it was experienced that it is not possible to build a Kubernetes ConfigMap from a folder recursively [4]. As the set of configuration files that need to be passed into the container is required to maintain the folder structure in this scenario, it was identified that using a persistent storage (containing the files with configuration changes) which could be shared among all the pods running containers from the specific Docker image is the best option to achieve the discussed goal. For this purpose, I tried using dynamic provisioning of persistent volumes [5]. But how can we pre-populate the dynamically provisioned persistent volume with the files with configuration changes? Your help, suggestions and concerns on this matter are highly appreciated. *Note*: Please find this [6] forum discussion I've initiated at Kubernetes Storage Special Interest Group [7]. [1]: https://github.com/wso2/kubernetes-ei [2]: Mail thread with subject "[Architecture] [Deployment] [Containers] An update to WSO2 product Dockerfile generalization" [3]: https://kubernetes-v1-4.github.io/docs/user-guide/configmap/ [4]: https://groups.google.com/forum/#!topic/kubernetes-users/h_FRSr5wW00 [5]: https://kubernetes.io/blog/2017/03/dynamic-provisioning-and-storage-classes-kubernetes [6]: https://groups.google.com/forum/#!topic/kubernetes-sig-storage/qhd2HFd7nbg [7]: https://github.com/kubernetes/community/tree/master/sig-storage -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Get container IPs of scaled Marathon application members from inside a container
Hi all, please see the following [1] DC/OS forum question, which I have posted in relation with getting container IPs of scaled Marathon application members from inside a container, when building DC/OS resources for WSO2 Identity Server 5.4.1 based deployment patterns. Your suggestions and concerns are highly appreciated. [1]: https://groups.google.com/a/dcos.io/forum/#!topic/users/sSq4pUsnnMs -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Docker ReadMe is unclear
Hi all, FYI, all the product Docker and Docker Compose resource repositories were improved and heavily refined, recently (e.g. latest Docker and Docker Compose resources for WSO2 Identity Server can be found from [1]). This includes well revised README documentation. Please see mail thread with subject [2] for detailed information on this effort. [1]: https://github.com/wso2/docker-is/tree/master [2]: [Architecture] [Deployment] [Containers] Refining WSO2 Dockerfile structure On Wed, Nov 1, 2017 at 3:17 PM, Saneth Dharmakeerthi wrote: > Hi Aparna, > > How to build the Docker image and running steps are mention in the ReadMe > file inside the dockerfile folder[1]. > > Agreed with you, There should be a link form root ReadMe file to this one. > > [1] https://github.com/wso2/docker-is/tree/release-5.3.0/dockerfile > > Thanks and Best Regards, > > Saneth Dharmakeerthi > *Associate Technical Lead* > WSO2, Inc. > Mobile: +94772325511 <+94%2077%20232%205511> > > <http://wso2.com/signature> > > On Tue, Oct 31, 2017 at 3:37 PM, Aparna Karunarathna > wrote: > >> Hi All, >> >> Docker images creating steps are not clear. >> >> I have configured the K8S cluster and then started creating the docker >> images. In order to do that, I followed the link [1] ReadMe, after >> executing the last command "git submodule update" there's no way to find >> out what to do next? >> >> Seems like this is common to all docker repos. >> >> >> [1] https://github.com/wso2/docker-is/tree/release-5.3.0 >> >> -- >> *Regards,* >> >> *Aparna Karunarathna.* >> >> >> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* >> >> * <http://wso2.com/signature>* >> >> ___ >> 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 > > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] BOSH Releases for WSO2 Identity Server Released!
WSO2 Installation Experience team is pleased to announce the release of BOSH Releases for WSO2 Identity Server 5.4.0. In this release, BOSH Releases for WSO2 Identity Server deployment patterns have been introduced. *Released Artifacts:* - https://github.com/wso2/pivotal-cf-is/releases/tag/v5.4.0.1 *Issues:* - https://github.com/wso2/pivotal-cf-is/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org - User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding BOSH releases by creating issues. Thank you! WSO2 Installation Experience Team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 <+94%2077%20593%200497> *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] WSO2 Docker and Docker Compose Resources Released!
WSO2 Installation Experience team is pleased to announce the release of WSO2 Docker resources for following products. - WSO2 API Manager 2.1.0 - WSO2 Identity Server 5.4.1 - WSO2 Enterprise Integrator 6.1.1 In this release, changes were made to improve the installation experience of Docker resources. Few major changes include: - Simplifying Docker image build process - Remove production deployment patterns from Docker Compose - Restructure Docker Compose for evaluation purposes *Released Artifacts:* - WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/releases/tag/v6.1.1.2 - WSO2 API Manager - https://github.com/wso2/docker-apim/releases/tag/v2.1.0.2 - WSO2 Identity Server - https://github.com/wso2/docker-is/releases/tag/v5.4.1.1 *Issues:* - WSO2 Enterprise Integrator - https://github.com/wso2/docker-ei/issues - WSO2 API Manager - https://github.com/wso2/docker-apim/issues - WSO2 Identity Server - https://github.com/wso2/docker-is/issues *How You Can Contribute* Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org - User List: u...@wso2.org *Reporting Issues* We encourage you to report issues and documentation faults regarding WSO2 Docker resources through respective repositories by creating issues. Thank you! WSO2 Installation Experience Team. -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Moving from BOSH deployment manifest schema v1 to v2
Hi all, while working on BOSH releases for WSO2 Identity Server deployment patterns, I encountered the existing deployment manifest implementations which utilize v1 schema [1]. Upon research of existing, popular BOSH release samples (e.g. zookeeper sample [2]) and references, it was identified that v2 schema [3] has been heavily used. For testing purposes, I managed to build up a sample deployment manifest using v2 schema, for WSO2 Identity Server deployment pattern 1. A primary difference that was identified was that the *networks* section which existed within the deployment manifest had to be defined as part of the *cloud-config.yml* file of the desired IaaS. Plus, the use of v2 schema effectively removed the occurrence of the deprecation warning regarding the *networks* section which was constantly experienced when running job tasks in existing BOSH release implementations ([4] and [5]). The earlier defined difference of the location of the *networks* section was the reason for this warning message. *Task 3 | 04:49:36 | Deprecation: Ignoring cloud config. Manifest contains 'networks' section.* If the use of manifest v2 schema is adopted, it is required to request the user to edit the *cloud-config.yml* file of the desired IaaS, to update the *networks* configurations (prior to deployment). Plus, the user has to update the current cloud-config.yml using the BOSH Command Line Interface (CLI). IMO, it would be better to move to using v2 schema due to its wide usage and as it separates out infrastructure specific details from those that are not [6]. Plus, from my personal experience it was identified that v1 schema leads to redundancy in some configurations defined. Shall we move to using deployment manifest schema v2? WDYT? [1]: https://bosh.io/docs/deployment-manifest.html [2]: https://github.com/cppforlife/zookeeper-release/blob/master/manifests/ zookeeper.yml [3]: https://bosh.io/docs/manifest-v2.html [4]: https://github.com/wso2/pivotal-cf-apim [5]: https://github.com/wso2/pivotal-cf-is [6]: https://ultimateguidetobosh.com/deployment-manifests-part-1/#cloud-config-part-1 -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 <+94%2077%20593%200497> *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Artifact synchronization in WSO2 Identity Server deployment patterns in Cloud Foundry BOSH
Hi all, please find the following issues in GitHub ([1] and [2]) which refer to discussions which I initiated at Cloud Foundry BOSH official repository with regards to this issue. Based on @Imesh's feedback and the discussions highlighted below, it was understood that this has to be performed through manual mounting of a NFS volume to VM instances. When using BOSH Lite, host NFS volume mounting was not possible as jobs were run within containers within Cloud Foundry's Warden container implementation present inside the BOSH Director VM [2]. One suggestion which came up was to create a new job which configures a NFS server in a container, which can be referred from other job containers [1]. [1]: https://github.com/cloudfoundry/bosh/issues/1881 [2]: https://github.com/cloudfoundry/bosh/issues/1882 On Mon, Jan 29, 2018 at 6:38 PM, Imesh Gunaratne wrote: > Hi Chiranga, > > On Fri, Jan 26, 2018 at 12:11 PM, Imesh Gunaratne wrote: > >> ... >> >> At the same time we can check with the BOSH team whether they have >> already implemented a solution for this. >> > > I checked this with the PCF engineering team and according to them we may > need to handle this manually using the BOSH release. There seems to be no > support from the BOSH Director to handle this based on the infrastructure > platform. > > Thanks > Imesh > >> >> [1] https://bosh.io/docs/deployment-manifest.html#properties >> >> Thanks >> Imesh >> >> On Thu, Jan 25, 2018 at 3:20 PM, Chiranga Alwis >> wrote: >> >>> Hi all, >>> >>> currently I am working on implementing Cloud Foundry (CF) BOSH releases >>> and Pivotal Cloud Foundry (PCF) Tiles for WSO2 Identity Server deployment >>> patterns. >>> >>> Currently, it has been understood that that there is no known concept in >>> BOSH for sharing volumes between BOSH instances [1]. >>> >>> Upon research it was learnt that if needed to share volumes, the >>> deployment is required to include a Network File System (NFS) or a similar >>> network files system service running on top of the BOSH instances. >>> >>> Currently, I am looking into how we can achieve this target. >>> >>> Your thoughts and suggestions are highly appreciated. >>> >>> [1]: https://ultimateguidetobosh.com/instances/#persistent-volumes >>> >>> -- >>> Yours sincerely, >>> >>> *Chiranga Alwis* >>> Software Engineer | WSO2 >>> >>> *Mobile : *+94775930497 <+94%2077%20593%200497> >>> *Email: *chirangaal...@gmail.com >>> *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 >>> *Medium:* https://medium.com/@chirangaalwis >>> >>> <http://wso2.com/signature> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Imesh Gunaratne* >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057> >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > > -- > *Imesh Gunaratne* > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057> > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Artifact synchronization in WSO2 Identity Server deployment patterns in Cloud Foundry BOSH
Hi all, currently I am working on implementing Cloud Foundry (CF) BOSH releases and Pivotal Cloud Foundry (PCF) Tiles for WSO2 Identity Server deployment patterns. Currently, it has been understood that that there is no known concept in BOSH for sharing volumes between BOSH instances [1]. Upon research it was learnt that if needed to share volumes, the deployment is required to include a Network File System (NFS) or a similar network files system service running on top of the BOSH instances. Currently, I am looking into how we can achieve this target. Your thoughts and suggestions are highly appreciated. [1]: https://ultimateguidetobosh.com/instances/#persistent-volumes -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 <+94%2077%20593%200497> *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Purpose of BOSH package 'common'
Hi all, when analyzing the existing PCF BOSH implementations [1] [2], I encountered a package defined named 'common'. The rationale behind the existence of this package is not clear to me. As you may know, BOSH packages provide the required information to prepare the binaries and dependencies for the jobs we define [3]. Your help, ideas and suggestions are highly appreciated. [1]: https://github.com/wso2/pivotal-cf-is [2]: https://github.com/wso2/pivotal-cf-apim [3]: https://bosh.io/docs/create-release.html#pkg-skeletons -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Misspelled MySQL index name in MySQL 5.7 db script
Hi all, I encountered the following misspelled MySQL index name in MySQL 5.7 db script (/dbscripts/mysql5.7.sql). *CREATE INDEX REG_RESOURCE_IND_BY_TENAN USING HASH ON REG_RESOURCE(REG_TENANT_ID, REG_UUID);* in which '*REG_RESOURCE_IND_BY_TENAN' *index name should ideally change to ' *REG_RESOURCE_IND_BY_TENANT*', according to my belief. WDYT? -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] AWS CloudFormation for WSO2 API Manager 2.1.0
Hi, the WSO2 Installer Experience team is pleased to announce the release of AWS CloudFormation for WSO2 API Manager 2.1.0. This is the first release of AWS CloudFormation resources for WSO2 API Manager version 2.1.0. It contains the WSO2 API Manager CloudFormation template and the resources required to create WSO2 API Manager and WSO2 API Manager Analytics Amazon Machine Images (AMIs). The source and tag location for this release are available from here <https://github.com/wso2/cloudformation-apim/releases/tag/2.1.0.1>. WSO2 API Manager CloudFormation Template The deployment of current release is based on WSO2 API Manager deployment pattern-1 <https://docs.wso2.com/display/AM210/Deployment+Patterns#DeploymentPatterns-Pattern1>. It deploys two WSO2 API Manager nodes publishing statistics to one WSO2 API Manager Analytics node. The following AWS resources will be created: 1. Virtual Private Cloud (VPC) with two public subnets and two private subnets 2. Two API Manager Auto Scaling groups in private subnets 3. An API Manager Analytics Auto Scaling group in one of the private subnets 4. Relational Database Service (RDS) for API Manager and API Manager Analytics 5. Elastic File System (EFS) for artifact sharing 6. A NAT Gateway 7. An Internet Gateway 8. Amazon EC2 Security Groups 9. Elastic Load Balancing (ELB) for API Manager 10. Elastic Load Balancing (ELB) for API Manager Analytics Quick Start Guide https://github.com/wso2/cloudformation-apim/blob/master/README.md *Reporting issues* Issues can be reported to https://github.com/wso2/cloudformation-apim/issues . Thank you, WSO2 Installer Experience team -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 <+94%2077%20593%200497> *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Set static private IP addresses to AWS EC2 Instances registered with an AWS Elastic Load Balancer
Hi all, I have posted the following question in StackOverflow under the title corresponding to the mail subject. Any help, ideas and suggestions are highly appreciated. <http://goog_990863524> https://stackoverflow.com/questions/45648220/set-static- private-ip-addresses-to-aws-ec2-instances-registered-with-an-aws-elas -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 <+94%2077%20593%200497> *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] Clustering APIM 2.1.0
Hi, from WSO2 API Manager version 2.0.0 documentation: https://docs.wso2.com/display/AM200/Deploying+API+Manager+as+an+All-in-One+Instance . On Wed, Jul 26, 2017 at 9:02 AM, T C wrote: > Dear WSO2 > > Does instruction in [1] can be used for API Manager version 2.0.0? > > [1] https://docs.wso2.com/display/AM210/Deploying+API+ > Manager+as+an+All-in-One+Instance > > Thank you very much, > Tinnapat. > > On Tue, Jul 25, 2017 at 11:10 AM, Yasima Dewmini wrote: > >> Hi Javier, >> >> According to my understanding you need to cluster two API manager >> instances as All-in-One instance. That means all API Manager components - >> Publisher, Store, Gateway, Key Manager and Traffic Manager are deployed as >> one instance. >> >> There are two ways to achieve this. >> >> 1. >> >> *Active/passive deployment* >> In this scenario, one APIM instance will serve the API traffic while the >> other instance stays in passive mode. >> >> >> 2. >> >> *Active/Active deployment* >> In this scenario, both APIM instances will be in active mode and will >> serve the API traffic. >> >> >> >> >> In both cases, same database is shared with both APIM instances, so that >> no need of syncing tokens. >> For more information please refer [1]. >> >> [1] https://docs.wso2.com/display/AM210/Deploying+API+Manager+as >> +an+All-in-One+Instance >> >> Regards, >> Yasima >> >> On Tue, Jul 25, 2017 at 2:01 AM, Vazquez-Hidalgo, Javier < >> javier.vazquez-hida...@tdsecurities.com> wrote: >> >>> Hi, >>> >>> >>> >>> Is it possible to cluster two standalone APIM instances? >>> >>> >>> >>> LB | -- APIM Standalone 1 à DB >>> >>> |--- APIM Standalone 2 >>> >>> >>> >>> If so, how do I sync tokens between the two instances? >>> >>> >>> >>> Thanks, >>> >>> Javier >>> >>> >>> >>> If you wish to unsubscribe from receiving commercial electronic messages >>> from TD Bank Group, please click here <http://www.td.com/tdoptout> or >>> go to the following web address: www.td.com/tdoptout >>> Si vous souhaitez vous désabonner des messages électroniques de nature >>> commerciale envoyés par Groupe Banque TD veuillez cliquer ici >>> <http://www.td.com/tddesab> ou vous rendre à l'adresse >>> www.td.com/tddesab >>> >>> >>> NOTICE: Confidential message which may be privileged. Unauthorized >>> use/disclosure prohibited. If received in error, please go to >>> www.td.com/legal for instructions. >>> AVIS : Message confidentiel dont le contenu peut être privilégié. >>> Utilisation/divulgation interdites sans permission. Si reçu par erreur, >>> prière d'aller au www.td.com/francais/avis_juridique pour des >>> instructions. >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> http://wso2.com/signatureYasima Dewmini >> Software Engineer, WSO2, Inc. >> Email: yas...@wso2.com >> Mobile: +94713117081 <+94%2071%20311%207081> >> >> ___ >> 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 > > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] Clustering APIM 2.1.0
Hi all, FYI we would be making this solution available on AWS Marketplace, for use in the near future. On Tue, Jul 25, 2017 at 9:40 AM, Yasima Dewmini wrote: > Hi Javier, > > According to my understanding you need to cluster two API manager > instances as All-in-One instance. That means all API Manager components - > Publisher, Store, Gateway, Key Manager and Traffic Manager are deployed as > one instance. > > There are two ways to achieve this. > > 1. > > *Active/passive deployment* > In this scenario, one APIM instance will serve the API traffic while the > other instance stays in passive mode. > > > 2. > > *Active/Active deployment* > In this scenario, both APIM instances will be in active mode and will > serve the API traffic. > > > > > In both cases, same database is shared with both APIM instances, so that > no need of syncing tokens. > For more information please refer [1]. > > [1] https://docs.wso2.com/display/AM210/Deploying+API+Manager+ > as+an+All-in-One+Instance > > Regards, > Yasima > > On Tue, Jul 25, 2017 at 2:01 AM, Vazquez-Hidalgo, Javier < > javier.vazquez-hida...@tdsecurities.com> wrote: > >> Hi, >> >> >> >> Is it possible to cluster two standalone APIM instances? >> >> >> >> LB | -- APIM Standalone 1 à DB >> >> |--- APIM Standalone 2 >> >> >> >> If so, how do I sync tokens between the two instances? >> >> >> >> Thanks, >> >> Javier >> >> >> >> If you wish to unsubscribe from receiving commercial electronic messages >> from TD Bank Group, please click here <http://www.td.com/tdoptout> or go >> to the following web address: www.td.com/tdoptout >> Si vous souhaitez vous désabonner des messages électroniques de nature >> commerciale envoyés par Groupe Banque TD veuillez cliquer ici >> <http://www.td.com/tddesab> ou vous rendre à l'adresse www.td.com/tddesab >> >> >> NOTICE: Confidential message which may be privileged. Unauthorized >> use/disclosure prohibited. If received in error, please go to >> www.td.com/legal for instructions. >> AVIS : Message confidentiel dont le contenu peut être privilégié. >> Utilisation/divulgation interdites sans permission. Si reçu par erreur, >> prière d'aller au www.td.com/francais/avis_juridique pour des >> instructions. >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > http://wso2.com/signatureYasima Dewmini > Software Engineer, WSO2, Inc. > Email: yas...@wso2.com > Mobile: +94713117081 <+94%2071%20311%207081> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *chirangaal...@gmail.com *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Possible Bug Reports
Hi Sagar,
can you please specify the WSO2 Data Analytics Server version you are
using, as well?
On Thu, Jul 20, 2017 at 11:00 PM, Chiranga Alwis wrote:
> Hi Sagar,
>
> it would be helpful if you could share the code mentioned in part a. of
> your question.
>
> On Thu, Jul 20, 2017 at 1:02 PM, Chandana Napagoda
> wrote:
>
>> +Chiranga
>>
>> On Thu, Jul 20, 2017 at 11:39 AM, Sagar Kapadia
>> wrote:
>>
>>>
>>> -- Forwarded message --
>>> From: Sagar Kapadia
>>> Date: Wed, Jul 19, 2017 at 5:05 PM
>>> Subject: Possible Bug Reports
>>> To: dev-requ...@wso2.org, ash...@avinashi.com,
>>> sa...@cloudnineconsulting.in
>>>
>>>
>>> Hi,
>>> a. Custom OSGI components are not recognized.
>>> I created a custom event publisher and copied the jar to dropins folder.
>>> The start method of the Activator class was called. But the activate method
>>> was never called. I can share the code if required
>>> This issue has been reported by someone else previously.
>>> https://wso2.org/jira/browse/CARBON-12728
>>>
>>> I have updated to latest version using WUM.
>>>
>>> b. The documentation of sample to create a custom event publisher is out
>>> of date. The classes have been replaced by interfaces and vice versa in the
>>> present version of the library
>>>
>>> c. Console doesnt show up in windows 7 , similar to this question on
>>> SO, which hasnt been
>>> answered yet
>>>
>>> https://stackoverflow.com/questions/43608516/new-with-wso2-das
>>> d. The Http Publisher writes events to the Trace, but does not actually
>>> do a POST. The configuration is as below
>>>
>>> >> trace="enable" xmlns="http://wso2.org/carbon/eventpublisher";>
>>>
>>>
>>>
>>>
>>> HttpPost
>>> https://requestb.in/1atd4211
>>>
>>>
>>> and traces are
>>> 16:51:26,157 [-] [Grizzly(2)] INFO EVENT_TRACE_LOGGER TenantId : -1234,
>>> Event Publisher : RequestBinPublihser2, after processing
>>> {"event":{"metaData":{"payload":"RT @WernWatt: Net terug van
>>> #bzacongres The future of firefighting #SmartCity #WearableTechnology
>>> #verdomdInteressant https://t.co/6AqhU6r3…","topic
>>> ":"tweets/gesucfator1978"},"payloadData":{"id":887633471555993600,"text":"RT
>>> @WernWatt: Net terug van #bzacongres The future of firefighting #SmartCity
>>> #WearableTechnology #verdomdInteressant https://t.co/6AqhU6r3…","creat
>>> ed_on":null}}}
>>>
>>>
>>>
>>> I would have filed a bug report, but have forgotten my password and am
>>> unable to login.
>>> I sent a mail regarding this, but have not received any reply yet.
>>> Please confirm whether this bug exists.
>>>
>>> We are evaluating WSO2 Data Analytics Server, and need to know if there
>>> is a bug, or we should be doing something differently.
>>> Sincerely,
>>> Sagar R. Kapadia
>>>
>>>
>>> _______
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email : chand...@wso2.com **Mobile : +94718169299
>> <+94%2071%20816%209299>*
>>
>> *Blog :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>
>> | http://chandana.napagoda.com <http://chandana.napagoda.com>*
>>
>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>> <http://www.linkedin.com/in/chandananapagoda>*
>>
>>
>
>
> --
> Yours sincerely,
>
> *Chiranga Alwis*
> Software Engineer | WSO2
>
> *Mobile : *+94775930497 <+94%2077%20593%200497>
> *Email: *chirangaal...@gmail.com
> *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
>
> <http://wso2.com/signature>
>
--
Yours sincerely,
*Chiranga Alwis*
Software Engineer | WSO2
*Mobile : *+94775930497
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Possible Bug Reports
Hi Sagar,
it would be helpful if you could share the code mentioned in part a. of
your question.
On Thu, Jul 20, 2017 at 1:02 PM, Chandana Napagoda
wrote:
> +Chiranga
>
> On Thu, Jul 20, 2017 at 11:39 AM, Sagar Kapadia
> wrote:
>
>>
>> -- Forwarded message --
>> From: Sagar Kapadia
>> Date: Wed, Jul 19, 2017 at 5:05 PM
>> Subject: Possible Bug Reports
>> To: dev-requ...@wso2.org, ash...@avinashi.com,
>> sa...@cloudnineconsulting.in
>>
>>
>> Hi,
>> a. Custom OSGI components are not recognized.
>> I created a custom event publisher and copied the jar to dropins folder.
>> The start method of the Activator class was called. But the activate method
>> was never called. I can share the code if required
>> This issue has been reported by someone else previously.
>> https://wso2.org/jira/browse/CARBON-12728
>>
>> I have updated to latest version using WUM.
>>
>> b. The documentation of sample to create a custom event publisher is out
>> of date. The classes have been replaced by interfaces and vice versa in the
>> present version of the library
>>
>> c. Console doesnt show up in windows 7 , similar to this question on SO,
>> which hasnt been
>> answered yet
>>
>> https://stackoverflow.com/questions/43608516/new-with-wso2-das
>> d. The Http Publisher writes events to the Trace, but does not actually
>> do a POST. The configuration is as below
>>
>> > trace="enable" xmlns="http://wso2.org/carbon/eventpublisher";>
>>
>>
>>
>>
>> HttpPost
>> https://requestb.in/1atd4211
>>
>>
>> and traces are
>> 16:51:26,157 [-] [Grizzly(2)] INFO EVENT_TRACE_LOGGER TenantId : -1234,
>> Event Publisher : RequestBinPublihser2, after processing
>> {"event":{"metaData":{"payload":"RT @WernWatt: Net terug van #bzacongres
>> The future of firefighting #SmartCity #WearableTechnology
>> #verdomdInteressant https://t.co/6AqhU6r3…","topic
>> ":"tweets/gesucfator1978"},"payloadData":{"id":887633471555993600,"text":"RT
>> @WernWatt: Net terug van #bzacongres The future of firefighting #SmartCity
>> #WearableTechnology #verdomdInteressant https://t.co/6AqhU6r3…","creat
>> ed_on":null}}}
>>
>>
>>
>> I would have filed a bug report, but have forgotten my password and am
>> unable to login.
>> I sent a mail regarding this, but have not received any reply yet.
>> Please confirm whether this bug exists.
>>
>> We are evaluating WSO2 Data Analytics Server, and need to know if there
>> is a bug, or we should be doing something differently.
>> Sincerely,
>> Sagar R. Kapadia
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email : chand...@wso2.com **Mobile : +94718169299
> <+94%2071%20816%209299>*
>
> *Blog :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>
> | http://chandana.napagoda.com <http://chandana.napagoda.com>*
>
> *Linkedin : http://www.linkedin.com/in/chandananapagoda
> <http://www.linkedin.com/in/chandananapagoda>*
>
>
--
Yours sincerely,
*Chiranga Alwis*
Software Engineer | WSO2
*Mobile : *+94775930497
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Natasha Wijesekara
Congratulations Natasha! On Wed, Jun 29, 2016 at 11:06 AM, Dileesha Rajapakse wrote: > Congratulations Natasha! > > On Wed, Jun 29, 2016 at 10:59 AM, Sajith Perera wrote: > >> Congratulations Natasha..!!! :) >> >> On Wed, Jun 29, 2016 at 10:49 AM, Natasha Wijesekara >> wrote: >> >>> Thank you all !!! >>> >>> On Wed, Jun 29, 2016 at 10:45 AM, Natasha Wijesekara >>> wrote: >>> >>>> Thank you akki ! :) >>>> >>>> On Wed, Jun 29, 2016 at 10:32 AM, Himasha Guruge >>>> wrote: >>>> >>>>> Congrats Natasha! :) >>>>> >>>>> On Wed, Jun 29, 2016 at 10:23 AM, Nandika Jayawardana < >>>>> nand...@wso2.com> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> It's my pleasure to announce Natasha Wijesekara as a WSO2 Committer. >>>>>> Natasha has been a great contributor to BPS and PC products and in >>>>>> recognition of her contributions, she's been voted as a WSO2 Committer. >>>>>> >>>>>> Congratulations Natasha and keep up the good work! >>>>>> >>>>>> Regards >>>>>> Nandika >>>>>> >>>>>> -- >>>>>> Nandika Jayawardana >>>>>> WSO2 Inc ; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Himasha Guruge >>>>> *Software Engineer* >>>>> WS*O2* *Inc.* >>>>> Mobile: +94 777459299 >>>>> himas...@wso2.com >>>>> >>>> >>>> >>>> >>>> -- >>>> *Natasha Wijesekare* >>>> >>>> *Software Engineering Intern, WSO2 Inc: http://wso2.com >>>> <http://wso2.com/>* >>>> *email : nata...@wso2.com * >>>> *mobile: +94 771358651 <%2B94%20771358651>* >>>> >>> >>> >>> >>> -- >>> *Natasha Wijesekare* >>> >>> *Software Engineering Intern, WSO2 Inc: http://wso2.com >>> <http://wso2.com/>* >>> *email : nata...@wso2.com * >>> *mobile: +94 771358651 <%2B94%20771358651>* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sajith Dimal >> Software Engineer >> Mobile : +94783101496 >> WSO2 Inc. | http://wso2.com >> lean.enterprise.middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Dileesha Rajapakse > *Intern - Engineering* > Mobile : +94 (0) 772 555 933 > Tel : +94 112 741 505 > dilee...@wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Session fixation with Application Server 6.0.0 SAML 2.0 single-sign-on
Hi all, sure I follow that procedure in the future. On Tue, Jun 21, 2016 at 7:21 PM, Prabath Siriwardana wrote: > Hi Chiranga, > > On Tue, Jun 21, 2016 at 6:02 AM, Chiranga Alwis wrote: > >> Hi all, >> >> during the code review held last Friday, there was a discussion on >> session fixation. >> >> I performed a minor research on session fixation and checked out on >> measures taken by Tomcat internally to prevent such attacks. From what I >> have discovered it seems that Tomcat provides session fixation protection >> when a user authenticates his/her session by changing the session id. In my >> understanding this occurs during user authentication provided by Apache >> Tomcat. More details on this can be found from this >> <http://www.tomcatexpert.com/blog/2011/04/25/session-fixation-protection> >> article. >> >> When I checked the Tomcat source code further, I discovered that when it >> generates a session, it attempts to reuse the session id if one was >> submitted in a cookie, it does not reuse a session id if it is from a URL >> and uses the SSL session id if one is present. >> > > This issue is already fixed sometime back - and you can find all the > patches we have issued from wso2.com/security. > > Also if you report any security concerns in the future please report it to > secur...@wso2.com. > > Thanks & regards, > -Prabath > > >> >> This suggests that we may not have to consider a session id set in a URL. >> Hence, which further vulnerabilities exist within our system in relation >> with session fixation? >> >> -- >> Chiranga Alwis, >> Software Engineering Intern, >> +94 77 5930497 >> +94 77 6368208 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanks & Regards, > Prabath > > Twitter : @prabath > LinkedIn : http://www.linkedin.com/in/prabathsiriwardena > > Mobile : +1 650 625 7950 > > http://facilelogin.com > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Session fixation with Application Server 6.0.0 SAML 2.0 single-sign-on
Hi all, during the code review held last Friday, there was a discussion on session fixation. I performed a minor research on session fixation and checked out on measures taken by Tomcat internally to prevent such attacks. From what I have discovered it seems that Tomcat provides session fixation protection when a user authenticates his/her session by changing the session id. In my understanding this occurs during user authentication provided by Apache Tomcat. More details on this can be found from this <http://www.tomcatexpert.com/blog/2011/04/25/session-fixation-protection> article. When I checked the Tomcat source code further, I discovered that when it generates a session, it attempts to reuse the session id if one was submitted in a cookie, it does not reuse a session id if it is from a URL and uses the SSL session id if one is present. This suggests that we may not have to consider a session id set in a URL. Hence, which further vulnerabilities exist within our system in relation with session fixation? -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Vote] Release WSO2 Carbon Kernel 5.1.0 RC1
Hi all, I have tested the following features in a Unix system. - dropins capability during server startup - dropins tool - jar-to-OSGi-bundle converter functionality No issues found. [x] Stable - go ahead and release. On Mon, May 30, 2016 at 10:51 AM, Indika Sampath wrote: > Hi All, > > carbon 5.1.0-rc1 tested with andes (c5 migration) and product-mb (c5 > migration). I didn't found any issue. > > [x] Stable - go ahead and release > > Cheers! > > On Fri, May 27, 2016 at 6:15 PM, Niranjan Karunanandham > wrote: > >> Hi all, >> >> I have tested Carbon 5.1.0 RC1 with the following and found no issue. >> >>- Built carbon-datasources and tested a sample. >>- Built msf4j and tested the stockquote sample >>- Built carbon-caching and tested a sample >>- Tested JMX support by connect to the server via "Local Process" >> >> [x] Stable - go ahead and release >> >> Regards, >> Nira >> >> On Fri, May 27, 2016 at 5:19 PM, Nipuni Perera wrote: >> >>> Hi all, >>> >>> I have tested features below and no issues found. >>> >>>1. java.util.logging >>>2. built carbon-jndi and tested a sample >>> >>> [x] Stable - go ahead and release >>> >>> Thanks, >>> Nipuni >>> >>> On Fri, May 27, 2016 at 12:44 PM, Niranjan Karunanandham < >>> niran...@wso2.com> wrote: >>> >>>> Hi Devs, >>>> >>>> This is the 1st Release Candidate of WSO2 Carbon Kernel 5.1.0 >>>> >>>> This release fixed the following issues: >>>> https://wso2.org/jira/issues/?filter=13077 >>>> >>>> Please download and test your products with Kernel 5.1.0 RC1 and vote. >>>> >>>> *Source and binary distribution files:* >>>> >>>> https://github.com/wso2/carbon-kernel/releases/download/v5.1.0-rc1/wso2carbon-kernel-5.1.0.zip >>>> >>>> *Maven Staging repository:* >>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1020/ >>>> >>>> *The tag to be voted upon:* >>>> https://github.com/wso2/carbon-kernel/releases/tag/v5.1.0-rc1 >>>> >>>> [ ] Broken - do not releaes (explain why) >>>> [ ] Stable - go ahead and release >>>> >>>> Thank you, >>>> Carbon Team >>>> >>>> -- >>>> >>>> *Niranjan Karunanandham* >>>> Senior Software Engineer - WSO2 Inc. >>>> WSO2 Inc.: http://www.wso2.com >>>> >>> >>> >>> >>> -- >>> Nipuni Perera >>> Software Engineer; WSO2 Inc.; http://wso2.com >>> Email: nip...@wso2.com >>> Git hub profile: https://github.com/nipuni >>> Blog : http://nipunipererablog.blogspot.com/ >>> Mobile: +94 (71) 5626680 >>> <http://wso2.com> >>> >>> >> >> >> -- >> >> *Niranjan Karunanandham* >> Senior Software Engineer - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Indika Sampath > Senior Software Engineer > WSO2 Inc. > http://wso2.com > > Phone: +94 716 424 744 > Blog: http://indikasampath.blogspot.com/ > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] SAML 2.0 Single Logout Profile Response handling for AS 6.0.0
Hi,
I have been working on porting the past AS SAML 2.0 based single-sign-on
valve to the new AS version.
When refactoring and testing the already ported code, I came across the
following issue within the invoke() method of the SAML 2.0 SSO Tomcat Valve
[1].
In the group of if-then and if-then-else statements which handle the SAML
2.0 Web Browser SSO and Single-Logout Profiles, I find the following code
block which the program flow does not seem to enter within simple sign-in
and logout processes.
if (resolver.isSLORequest()) {
if (log.isDebugEnabled()) {
log.debug("Processing Single Log Out Request");
}
samlSSOManager = new SAML2SSOManager(ssoAgentConfig);
samlSSOManager.doSLO(request);
} else if (resolver.isSAML2SSOResponse()) {
During debugging of the past AS 5.3.0 implementation and my current
implementation, I have experienced that this block is never executed.
In addition, the implementation of the resolver.isSLORequest() method in
[2] has changed in latest versions and the carbon-identity version 4.5.6
(used in AS 5.3.0) possesses an older implementation [3]. I tried adopting
the new implementation which leads to an error during handling of
Single-Logout responses from the side of Identity Server.
Are there any scenarios which led to the introduction of the above
mentioned logic when performing SSO? Any suggestions or ideas are highly
appreciated.
[1] - SAMLSSOValve.java
<https://github.com/wso2/carbon-deployment/blob/4.6.x/components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/sso/SAMLSSOValve.java>
[2] - SSOAgentRequestResolver.java
<https://github.com/wso2-extensions/identity-agent-sso/blob/master/components/org.wso2.carbon.identity.sso.agent/src/main/java/org/wso2/carbon/identity/sso/agent/SSOAgentRequestResolver.java>
[3] - SSOAgentRequestResolver.java
<https://github.com/wso2/carbon-identity/blob/v4.5.6/components/agents/org.wso2.carbon.identity.sso.agent/src/main/java/org/wso2/carbon/identity/sso/agent/SSOAgentRequestResolver.java>
--
Chiranga Alwis,
Software Engineering Intern,
+94 77 5930497
+94 77 6368208
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Java LinkageError on AS 6.0.0 when webapp's contain libraries exist on server lib directory
+1 But shouldn't the naming of the module be more generic? Using "shaded" refers more towards the implementation where we have used the plugin Maven-Shade-Plugin. We have effectively relocated the classes. /modules/*relocated-libs* |- slf4j |- libthrift Isn't this a better naming convention? Plus, this module will have to be the first to be built among all Application Server modules' sub-modules since all other modules require it. On Tue, May 10, 2016 at 4:14 PM, Manoj Kumara wrote: > +1 > > *Manoj Kumara* > WSO2 Inc. *| **lean. enterprise. middleware.* > *Mobile:* +94 713 448188 > > On Tue, May 10, 2016 at 3:58 PM, KasunG Gajasinghe > wrote: > >> >> Yes, we need to avoid having common logging frameworks such as SLF4J in >> the classpath since it has a good possibility to lead to classloading >> issues for webapp developers . >> >> Since slf4j could be used by multiple jars, it should be a separate >> shaded jar. I believe the *artifactId* should reflect that it is shaded. >> Otherwise, the jar name will be confusing. So, shall we use the name >> *slf4j-shaded*? >> >> >> On Tue, May 10, 2016 at 3:40 PM, Kishanthan Thangarajah < >> kishant...@wso2.com> wrote: >> >>> +1, let's use the AS repo and at build time, which can get installed >>> during build time and this will also become part of release which will be >>> deployed onto nexus. >>> >>> Is the naming is correct? Shouldn't it be "shaded"? >>> >> >> +1. >> >> Thanks, >> KasunG >> >> >>> >>> On Tue, May 10, 2016 at 3:00 PM, Manoj Kumara wrote: >>> >>>> Hi Dev's, >>>> >>>> During testing WSO2AS 6.0.0 we encounters $Subject error when SLF4j >>>> library available on the webapp libs directory as /lib also >>>> contain the same library to be used by libthrift library used during stat >>>> publishing. After analyzing the issue with the team realized that this >>>> occurred as Tomcat has a flat class path and multiple package versions >>>> cannot be used as in OSGI runtime. >>>> >>>> To resolve this as per the recommendation provided by KasunG we used >>>> '*Maven >>>> Shade Plugin* [1]' to shade package name (rename package structure and >>>> usages) as other open-source projects like Tomcat, Maven use similar >>>> patterns when using commonly used packages. >>>> >>>> As these shaded libraries required for AS distribution these libs need >>>> to be maintained inside product it self I suggest to maintain them as below >>>> with '*org.wso2.shade*' prefix on groupID. Thoughts ? >>>> >>>> /modules/*shade-libs* >>>> |- slf4j >>>> |- libthrift >>>> >>>> [1] https://maven.apache.org/plugins/maven-shade-plugin/ >>>> >>>> >>>> Regards, >>>> Manoj >>>> >>> >>> >>> >>> -- >>> *Kishanthan Thangarajah* >>> Associate Technical Lead, >>> Platform Technologies Team, >>> WSO2, Inc. >>> lean.enterprise.middleware >>> >>> Mobile - +94773426635 >>> Blog - *http://kishanthan.wordpress.com >>> <http://kishanthan.wordpress.com>* >>> Twitter - *http://twitter.com/kishanthan >>> <http://twitter.com/kishanthan>* >>> >> >> >> >> -- >> >> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Handling non-OSGi JARs within dropins capability
Hi,
sorry for the lack of clarity Manuranga. The answer is no to your question.
It will only throw out a warning if it encounters a non-OSGi JAR and simply
skip processing that file. The other files will continue to be processed.
Simply, all the OSGi bundles' details in the dropins directory will be
updated in the bundles.info file while others will be left out.
On Thu, Apr 28, 2016 at 7:20 PM, Manuranga Perera wrote:
> Hi,
> Sorry, I was not asking about corrupted jars, asking about non-OSGi jars.
> Was wondering why you said "no *other *file(s) will be written to the
> bundles.info file of the particular profile, thus will not be picked up
> by the Carbon server". Does this means, if I have one non-OSGi jar in
> dropins some other OSGi jars will not get picked up?
>
> On Thu, Apr 28, 2016 at 1:13 AM, Chiranga Alwis wrote:
>
>> Hi Manuranga,
>>
>> in addition to the above checks in relation with filtering out non-OSGi
>> bundles, in order to access the JAR file Manifest to retrieve the required
>> Manifest headers, I am using java.util.jar.JarFile
>> <https://docs.oracle.com/javase/7/docs/api/java/util/jar/JarFile.html>
>> class. The code fragment within the getNewBundleInfo method, for retrieving
>> the Manifest information is as follows:
>>
>> try (JarFile jarFile = new JarFile(bundlePath.toString())) {
>> Manifest manifest = jarFile.getManifest();
>> if ((manifest == null) || (manifest.getMainAttributes() == null)) {
>> throw new IOException("Invalid OSGi bundle found in the " +
>> Constants.DROPINS +
>> " directory: " + jarFile.toString());
>> } else {
>> String bundleSymbolicName =
>> manifest.getMainAttributes().getValue("Bundle-SymbolicName");
>> String bundleVersion =
>> manifest.getMainAttributes().getValue("Bundle-Version");
>>
>> if (bundleSymbolicName == null || bundleVersion == null) {
>> throw new IOException(
>> "Required bundle manifest headers do not exist in " +
>> jarFile.toString());
>> } else {
>> if (bundleSymbolicName.contains(";")) {
>> bundleSymbolicName = bundleSymbolicName.split(";")[0];
>> }
>> }
>>
>> // checks whether this bundle is a fragment or not
>> boolean isFragment =
>> (manifest.getMainAttributes().getValue("Fragment-Host") != null);
>> int defaultBundleStartLevel = 4;
>> BundleInfo generated = new BundleInfo(bundleSymbolicName,
>> bundleVersion,
>> "../../" + Constants.DROPINS + "/" + fileName,
>> defaultBundleStartLevel, isFragment);
>> return Optional.of(generated);
>> }
>> }
>>
>> The above code fragment will be executed for every file path within the
>> dropins directory, which has a .jar extension. Since we are using the above
>> mentioned class, I believe that during the creation of the JarFile
>> <https://docs.oracle.com/javase/7/docs/api/java/util/jar/JarFile.html>
>> instance (for each file with a .jar extension) will be checked for a
>> corrupted JAR.
>>
>> The complete implementation of the above functionality can be accessed
>> from here
>> <https://github.com/wso2/carbon-kernel/tree/master/launcher/src/main/java/org/wso2/carbon/launcher/extensions>
>> .
>>
>>
>> On Wed, Apr 27, 2016 at 7:45 PM, Manuranga Perera wrote:
>>
>>> no *other *file(s) will be written to the bundles.info file of the
>>>> particular profile, thus will not be picked up by the Carbon server.
>>>>
>>>
>>> Any reason why not only faulty bundle is ignored ?
>>>
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com
>>>
>>
>>
>>
>> --
>> Chiranga Alwis,
>> Software Engineering Intern,
>> +94 77 5930497
>> +94 77 6368208
>>
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
--
Chiranga Alwis,
Software Engineering Intern,
+94 77 5930497
+94 77 6368208
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Handling non-OSGi JARs within dropins capability
Hi Manuranga,
in addition to the above checks in relation with filtering out non-OSGi
bundles, in order to access the JAR file Manifest to retrieve the required
Manifest headers, I am using java.util.jar.JarFile
<https://docs.oracle.com/javase/7/docs/api/java/util/jar/JarFile.html>
class. The code fragment within the getNewBundleInfo method, for retrieving
the Manifest information is as follows:
try (JarFile jarFile = new JarFile(bundlePath.toString())) {
Manifest manifest = jarFile.getManifest();
if ((manifest == null) || (manifest.getMainAttributes() == null)) {
throw new IOException("Invalid OSGi bundle found in the " +
Constants.DROPINS +
" directory: " + jarFile.toString());
} else {
String bundleSymbolicName =
manifest.getMainAttributes().getValue("Bundle-SymbolicName");
String bundleVersion =
manifest.getMainAttributes().getValue("Bundle-Version");
if (bundleSymbolicName == null || bundleVersion == null) {
throw new IOException(
"Required bundle manifest headers do not exist in
" + jarFile.toString());
} else {
if (bundleSymbolicName.contains(";")) {
bundleSymbolicName = bundleSymbolicName.split(";")[0];
}
}
// checks whether this bundle is a fragment or not
boolean isFragment =
(manifest.getMainAttributes().getValue("Fragment-Host") != null);
int defaultBundleStartLevel = 4;
BundleInfo generated = new BundleInfo(bundleSymbolicName, bundleVersion,
"../../" + Constants.DROPINS + "/" + fileName,
defaultBundleStartLevel, isFragment);
return Optional.of(generated);
}
}
The above code fragment will be executed for every file path within the
dropins directory, which has a .jar extension. Since we are using the above
mentioned class, I believe that during the creation of the JarFile
<https://docs.oracle.com/javase/7/docs/api/java/util/jar/JarFile.html>
instance (for each file with a .jar extension) will be checked for a
corrupted JAR.
The complete implementation of the above functionality can be accessed from
here
<https://github.com/wso2/carbon-kernel/tree/master/launcher/src/main/java/org/wso2/carbon/launcher/extensions>
.
On Wed, Apr 27, 2016 at 7:45 PM, Manuranga Perera wrote:
> no *other *file(s) will be written to the bundles.info file of the
>> particular profile, thus will not be picked up by the Carbon server.
>>
>
> Any reason why not only faulty bundle is ignored ?
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
--
Chiranga Alwis,
Software Engineering Intern,
+94 77 5930497
+94 77 6368208
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Handling non-OSGi JARs within dropins capability
Hi,
based on an off-line discussion, we decided to simply throw warnings within
the getNewBundlesInfo method loop if any of the above mentioned issue(s)
associated with a non-OSGi JAR is/are encountered.
This effectively means unless a particular file added to the dropins folder
is an OSGi JAR, no other file(s) will be written to the bundles.info file
of the particular profile, thus will not be picked up by the Carbon server.
And adding a non-OSGi JAR to the dropins folder will not halt the server
from starting.
On Tue, Apr 26, 2016 at 11:26 AM, Chiranga Alwis wrote:
> Hi,
>
> I have been working on improving the existing dropins capability within
> the Carbon-kernel.
>
> In the utility methods I am using for dropins, I have a method which reads
> in the files of a given source directory and construct OSGi Bundle
> Information (BundleInfo.java
> <https://github.com/wso2/carbon-kernel/blob/master/launcher/src/main/java/org/wso2/carbon/launcher/extensions/model/BundleInfo.java>)
> instances.
>
> public static List getNewBundlesInfo(Path sourceDirectory) throws
> IOException {
> List newBundleInfoLines = new ArrayList<>();
> if ((sourceDirectory != null) && (Files.exists(sourceDirectory))) {
> Stream children = Files.list(sourceDirectory);
> children.parallel().forEach(child -> {
> try {
> logger.log(Level.FINE, "Loading OSGi bundle information from
> " + child);
> getNewBundleInfo(child).ifPresent(newBundleInfoLines::add);
> logger.log(Level.FINE, "Successfully loaded OSGi bundle
> information from " + child);
> } catch (IOException e) {
> throw new RuntimeException("Error when loading the OSGi
> bundle information from " + child, e);
> }
> });
> } else {
> throw new IOException("Invalid OSGi bundle source directory: " +
> sourceDirectory);
> }
>
> return newBundleInfoLines;
> }
>
> Method getNewBundleInfo takes in a Path object and constructs the new
> BundleInfo instance if the appropriate conditions are satisfied.
>
> private static Optional getNewBundleInfo(Path bundlePath) throws
> IOException
>
> This method will throw an IOException in cases such as the following:
> - if the JAR manifest is not found.
> - if the OSGi Bundle-SymbolicName or the BundleVersion are not found
>
> The method returns Optional.empty() if the file does not have a .jar
> extension.
>
> In the above getNewBundlesInfo method, should I throw an exception when
> the loop encounters a non-OSGi JAR and stop the flow (currently, a
> RuntimeException is thrown to halt the processing) or should I continue
> processing the other directory files by simply issuing a warning when an
> invalid file is encountered?
> --
> Chiranga Alwis,
> Software Engineering Intern,
> +94 77 5930497
> +94 77 6368208
>
--
Chiranga Alwis,
Software Engineering Intern,
+94 77 5930497
+94 77 6368208
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Handling non-OSGi JARs within dropins capability
Hi,
I have been working on improving the existing dropins capability within the
Carbon-kernel.
In the utility methods I am using for dropins, I have a method which reads
in the files of a given source directory and construct OSGi Bundle
Information (BundleInfo.java
<https://github.com/wso2/carbon-kernel/blob/master/launcher/src/main/java/org/wso2/carbon/launcher/extensions/model/BundleInfo.java>)
instances.
public static List getNewBundlesInfo(Path sourceDirectory)
throws IOException {
List newBundleInfoLines = new ArrayList<>();
if ((sourceDirectory != null) && (Files.exists(sourceDirectory))) {
Stream children = Files.list(sourceDirectory);
children.parallel().forEach(child -> {
try {
logger.log(Level.FINE, "Loading OSGi bundle
information from " + child);
getNewBundleInfo(child).ifPresent(newBundleInfoLines::add);
logger.log(Level.FINE, "Successfully loaded OSGi
bundle information from " + child);
} catch (IOException e) {
throw new RuntimeException("Error when loading the
OSGi bundle information from " + child, e);
}
});
} else {
throw new IOException("Invalid OSGi bundle source directory: "
+ sourceDirectory);
}
return newBundleInfoLines;
}
Method getNewBundleInfo takes in a Path object and constructs the new
BundleInfo instance if the appropriate conditions are satisfied.
private static Optional getNewBundleInfo(Path bundlePath)
throws IOException
This method will throw an IOException in cases such as the following:
- if the JAR manifest is not found.
- if the OSGi Bundle-SymbolicName or the BundleVersion are not found
The method returns Optional.empty() if the file does not have a .jar
extension.
In the above getNewBundlesInfo method, should I throw an exception when the
loop encounters a non-OSGi JAR and stop the flow (currently, a
RuntimeException is thrown to halt the processing) or should I continue
processing the other directory files by simply issuing a warning when an
invalid file is encountered?
--
Chiranga Alwis,
Software Engineering Intern,
+94 77 5930497
+94 77 6368208
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unable to send SOAP call.
Hi, can you please provide the stack trace of the above instances of issues? On Mon, Mar 14, 2016 at 3:58 PM, Shakila Sivagnanarajah wrote: > Hi, > > I am implementing an authenticator for WSO2-IS-5.1.0. I am > getting [1] exception while getting instance of > *javax.xml.soap.SOAPConnectionFactory* like [2]. But I imported the " > *org.apache.axis2.saaj.**" in pom. How can I fix this issue? > > More Info: But did not get this error, if I use [3] to initiate the SOAP > connection. But getting [4] while building the SOAP message from response. > Since [5] is used to take instance of the SOAPMessage in > *org.apache.axis2.saaj.SOAPConnectionImpl* class. > > [1] Unable to create SOAP connection factory: Provider > *org.apache.axis2.saaj.SOAPConnectionFactoryImpl* not found > > [2] SOAPConnectionFactory soapConnectionFactory = > SOAPConnectionFactory.newInstance(); > > [3] SOAPConnection soapConnection = new > SOAPConnectionFactoryImpl().createConnection(); > > [4] Unable to create message factory for SOAP: Provider > *org.apache.axis2.saaj.MessageFactoryImpl* not found > > [5] > MessageFactory mf = MessageFactory.newInstance(); > SOAPMessage response = mf.createMessage(); > > > Thank you > -- > Shakila Sivagnanarajah > Associate Software Engineer > Mobile :+94 (0) 768 856837 > shak...@wso2.com > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.5 RC1
Hi all, I tested the following feature of AS 5.3.0: - SAML 2.0 based Single-Sign-On (SSO) with WSO2 Identity Server 5.1.0. This feature works as expected. [x] - Stable - go ahead and release. On Mon, Mar 14, 2016 at 6:53 PM, Niranjan Karunanandham wrote: > Hi all, > > Tested the following scenarios on AS: > > - User creation > - Role creation > - Tenant creation > - Artifact deployment of CApps, webapps, and axis2 services > - Axis2 Services/ Try-it > > [x] - Stable - go ahead and release. > > Regards, > Nira > > > On Sat, Mar 12, 2016 at 7:59 AM, Chandana Napagoda > wrote: > >> Hi, >> >> Verified following scenarios. >> - G-Reg product level integration tests >> - G-Reg getting started data population. >> - Did a smoke test in GC Store and Publisher >> - Enabled and Verified known test failures with kernel 4.4.4 releases. >> >> [x] Stable - go ahead and release. >> >> [1]. https://wso2.org/jira/browse/REGISTRY-3358 >> >> Regards, >> Chandana >> >> On Thu, Mar 10, 2016 at 6:34 PM, Niranjan Karunanandham < >> niran...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.5. >>> >>> This release fixes the following issues: >>> https://wso2.org/jira/issues/?filter=12978 >>> >>> Please download and test your products with kernel 4.4.5 RC1 and vote. >>> Vote will be open for 72 hours or as longer as needed. >>> >>> *Source and binary distribution files:* >>> >>> http://svn.wso2.org/repos/wso2/people/niranjan/Carbon-4.4.5/wso2carbon-4.4.5.zip >>> >>> *Maven staging repository:* >>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-402/ >>> >>> *The tag to be voted upon:* >>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.5-RC1 >>> >>> >>> [ ] Broken - do not release (explain why) >>> [ ] Stable - go ahead and release >>> >>> Thank you >>> Carbon Team >>> >>> -- >>> >>> *Niranjan Karunanandham* >>> Senior Software Engineer - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Chandana Napagoda* >> Senior Software Engineer >> WSO2 Inc. - http://wso2.org >> >> *Email : chand...@wso2.com **Mobile : +94718169299 >> <%2B94718169299>* >> >> *Blog :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>* >> >> > > > -- > > *Niranjan Karunanandham* > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 5.0.0 RC2
Hi, I tested the following aspects: - jar-to-OSGi-bundle converter - converted OSGi bundles in dropins folder being successfully deployed No issues discovered. [x] Stable - go ahead and release. On Sun, Dec 20, 2015 at 11:27 AM, Senduran Balasubramaniyam < sendu...@wso2.com> wrote: > Hi all, > > I have tested product-gw's basic functionality with this release > candidate. > No issues found. > > [x] Stable - go ahead and release > > Regards > Senduran > > On Sun, Dec 20, 2015 at 10:01 AM, Aruna Karunarathna > wrote: > >> I've tested, the following features >> >> 1. Logging framework >> 2. Transport Management >> 3. Jar to bundle conversion >> 4. Dropins bundle deployment >> >> [x] Stable - go ahead and release >> >> Regards, >> Aruna >> >> On Sat, Dec 19, 2015 at 11:50 PM, Manuri Amaya Perera >> wrote: >> >>> Hi, >>> >>> I created projects using the available archetypes in staging repository >>> and built and installed via dropins and osgi console and tested the >>> expected functionality with the kernel 5.0.0 RC2 pack. >>> >>> [x] Stable - go ahead and release. >>> >>> Thank you. >>> >>> On Fri, Dec 18, 2015 at 5:15 PM, Kishanthan Thangarajah < >>> kishant...@wso2.com> wrote: >>> >>>> Hi Devs, >>>> >>>> This is the 2nd Release Candidate of WSO2 Carbon Kernel 5.0.0. >>>> >>>> This release fixes the following issues: >>>> https://wso2.org/jira/issues/?filter=12581 >>>> >>>> Please download and test your products with kernel 5.0.0 RC2 and vote. >>>> >>>> *Source and binary distribution files:* >>>> >>>> https://github.com/wso2/carbon-kernel/releases/download/v5.0.0-RC2/wso2carbon-kernel-5.0.0-rc2.zip >>>> >>>> *Maven staging repository:* >>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-210/ >>>> >>>> *The tag to be voted upon:* >>>> https://github.com/wso2/carbon-kernel/releases/tag/v5.0.0-RC2 >>>> >>>> >>>> [ ] Broken - do not release (explain why) >>>> [ ] Stable - go ahead and release >>>> >>>> Thank you, >>>> Carbon Team >>>> >>>> -- >>>> *Kishanthan Thangarajah* >>>> Associate Technical Lead, >>>> Platform Technologies Team, >>>> WSO2, Inc. >>>> lean.enterprise.middleware >>>> >>>> Mobile - +94773426635 >>>> Blog - *http://kishanthan.wordpress.com >>>> <http://kishanthan.wordpress.com>* >>>> Twitter - *http://twitter.com/kishanthan >>>> <http://twitter.com/kishanthan>* >>>> >>> >>> >>> >>> -- >>> >>> *Manuri Amaya Perera* >>> >>> *Software Engineer* >>> >>> *WSO2 Inc.* >>> >>> *Blog: http://manuriamayaperera.blogspot.com >>> <http://manuriamayaperera.blogspot.com>* >>> >> >> >> >> -- >> >> *Aruna Sujith Karunarathna *| Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 9040362 | Work: +94 112145345 >> Email: ar...@wso2.com | Web: www.wso2.com >> >> > > > > -- > *Senduran * > Software Engineer, > WSO2, Inc.; http://wso2.com/ <http://wso2.com/> > Mobile: +94 77 952 6548 > -- Chiranga Alwis, Software Engineering Intern, +94 77 5930497 +94 77 6368208 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
