Re: [Architecture] [Dev] [DEV] [VOTE] Release WSO2 API Manager Tooling v3.1.0 RC4
Hi all Tested apictl with followings. 1. Install k8s api-operator and wso2am-operator in a k8s cluster 2. Tested API Operator scenarios with the apictl 3. Added environments and import the APIs 4. Generated keys for the imported APIs 5. Uninstall the API Operator using apictl No blockers found *[+] Stable - Go ahead and release* *Thanks* On Sat, Apr 4, 2020 at 11:50 AM Pubudu Gunatilaka wrote: > Hi, > > Tested the apictl for the basic use cases of K8s API Operator. No blockers > found. > > [+] Stable - Go ahead and release > > Thank you! > > On Sat, Apr 4, 2020 at 9:36 AM Renuka Fernando wrote: > >> Hi all >> >> Tested apictl with followings. >> >>1. Install k8s api-operator in a k8s cluster >> - Batch mode (non interactive) with registry types: HTTP private >> registry, DockerHub >> - Interactive mode with registry types: GCR, AWS ECR >>2. Install k8s wso2am-operator >>3. Add a new API to k8s cluster using the "apictl add api" command. >> - With one replica >> - With two replicas >>4. Add a new API with multiple swaggers to k8s cluster using the "apictl >>add api" command. >>5. Update an API in k8s cluster. >>6. Change docker registry type for adding API to the k8s cluster. >> - Batch mode (non interactive) with registry types: AWS ECR >> - Interactive mode with registry types: AWS ECR >> >> >> No blockers found >> >> *[+] Stable - Go ahead and release* >> >> Thanks >> Best Regards >> >> *Renuka Fernando* | Software Engineer | WSO2 Inc. >> (m) +9476 6678 752 | Email: ren...@wso2.com >> <http://wso2.com/signature> >> >> >> On Fri, Apr 3, 2020 at 7:10 PM Uvindra Dias Jayasinha >> wrote: >> >>> Tested the following: >>> >>> Various scenarios involving super tenant, tenant, secondary user store >>> users >>> >>> 1. Generate Keys >>> 2. Export Apps >>> >>> No blockers found >>> >>> [+] Stable - Go ahead and release >>> >>> On Fri, 3 Apr 2020 at 14:16, Naduni Pamudika wrote: >>> >>>> Hi All, >>>> >>>> WSO2 Api Manager team is pleased to announce the fourth release >>>> candidate of WSO2 API Manager Tooling 3.1.0 version. >>>> >>>> The WSO2 API Manager tooling provides the capability to import and >>>> export APIs and Applications across multiple environments seamlessly. Hence >>>> it provides greater flexibility to create CI/CD pipelines for APIs and >>>> applications. >>>> >>>> Apart from migrating APIs and applications, it supports Kubernetes API >>>> operator to deploy and manage APIs in the Kubernetes cluster by reducing >>>> additional overheads for the DevOps. >>>> >>>> Please find the improvements and fixes related to this release in Fixed >>>> Issues >>>> <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aissue+is%3Aclosed+label%3A3.1.0> >>>> . >>>> >>>> Download the API Manager Tooling Distribution from here >>>> <https://github.com/wso2/product-apim-tooling/releases/tag/v3.1.0-rc4>. >>>> >>>> The tag to be voted upon is >>>> https://github.com/wso2/product-apim-tooling/releases/tag/v3.1.0-rc4 >>>> >>>> Documentation: >>>> https://apim.docs.wso2.com/en/next/learn/api-controller/getting-started-with-wso2-api-controller/ >>>> >>>> Please download, test the tool and vote. >>>> >>>> >>>> *[+] Stable - Go ahead and release* >>>> >>>> *[-] Broken - Do not release *(explain why) >>>> >>>> >>>> >>>> Best Regards, >>>> WSO2 API Manager Team >>>> >>>> -- >>>> *Naduni Pamudika* | Senior Software Engineer | WSO2 Inc. >>>> (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> >>>> >>> >>> -- >>> Regards, >>> Uvindra >>> >>> Mobile: 33962 >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> ___ >> Dev mailing list >> d...@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Pubudu Gunatilaka* | Technical Lead | WSO2 Inc. > (m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com > <http://wso2.com/signature> > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [Vote] Release of WSO2 API Manager 3.1.0 RC3
>>>>>>>> >>>>>>>>>>>> We are pleased to announce the third release candidate of WSO2 >>>>>>>>>>>> API Manager 3.1.0. >>>>>>>>>>>> >>>>>>>>>>>> This release fixes the following issues. >>>>>>>>>>>> >>>>>>>>>>>>- Fixes : product-apim >>>>>>>>>>>> >>>>>>>>>>>> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2019-11-01..2020-03-20+label%3A3.1.0+> >>>>>>>>>>>>- Fixes : analytics-apim >>>>>>>>>>>><https://github.com/wso2/analytics-apim/milestone/20?closed=1> >>>>>>>>>>>> >>>>>>>>>>>> Source and distribution, >>>>>>>>>>>> Runtime : >>>>>>>>>>>> https://github.com/wso2/product-apim/releases/tag/v3.1.0-rc3 >>>>>>>>>>>> Analytics : >>>>>>>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v3.1.0-rc3 >>>>>>>>>>>> >>>>>>>>>>>> Please download, test the product and vote. >>>>>>>>>>>> >>>>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> WSO2 API Manager Team >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> *Krishan Wijesena* >>>>>>>>>>>> Senior Software Engineer | WSO2 >>>>>>>>>>>> >>>>>>>>>>>> Email : krish...@wso2.com >>>>>>>>>>>> Mobile : +94776219923 >>>>>>>>>>>> WSO2 Inc : http://wso2.com >>>>>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> *Tharindu Dharmarathna*Technical Lead >>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>> >>>>>>>>>>> mobile: *+94779109091* >>>>>>>>>>> ___ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> d...@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Sanjula Madurapperuma* | Software Engineering Intern | WSO2 Inc. >>>>>>>>>> (m) +94 768877766 | (e) sanj...@wso2.com >>>>>>>>>> <http://wso2.com/signature> >>>>>>>>>> ___ >>>>>>>>>> Architecture mailing list >>>>>>>>>> Architecture@wso2.org >>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Nuwan Dias* | Senior Director | WSO2 Inc. >>>>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> d...@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Krishan Wijesena* >>>>>>>> Senior Software Engineer | WSO2 >>>>>>>> >>>>>>>> Email : krish...@wso2.com >>>>>>>> Mobile : +94776219923 >>>>>>>> WSO2 Inc : http://wso2.com >>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Krishan Wijesena* >>>>>>> Senior Software Engineer | WSO2 >>>>>>> >>>>>>> Email : krish...@wso2.com >>>>>>> Mobile : +94776219923 >>>>>>> WSO2 Inc : http://wso2.com >>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> Architecture@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. >>>>>> (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com >>>>>> GET INTEGRATION AGILE >>>>>> Integration Agility for Digitally Driven Business >>>>>> ___ >>>>>> Dev mailing list >>>>>> d...@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc. >>>>> +94 710 618 178 >>>>> GET INTEGRATION AGILE >>>>> Integration Agility for Digitally Driven Business >>>>> ___ >>>>> Dev mailing list >>>>> d...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> ___ >>>> Dev mailing list >>>> d...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> *Vithursa Mahendrarajah* | Senior Software Engineer | WSO2 Inc >>> (m) +94 766 695 643 | (e) vithu...@wso2.com >>> >>> * <http://wso2.com/signature>[image: https://wso2.com/signature] >>> <https://wso2.com/signature>* >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Kavishka Fernando* >> *Senior Software Engineer | WSO2* >> Email: kavis...@wso2.com >> Mobile: +94773838069 >> Web: http://wso2.com >> Blog: https://medium.com/@kavishkafernando >> >> <http://wso2.com/signature> >> ___ >> Dev mailing list >> d...@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > > *Sachini De Silva* > Senior Software Engineer - WSO2 > > Email : sachi...@wso2.com > Mobile : +94714765495 > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Improving the K8S API Operator First-Hand Experience
Hi Renuka/all, Hi all > > As of now, *API Operator*[1] requires a lot of configurations if someone > needs to *try it out *(PoC/quick start/demo). This breaks the user > experience and will lose the interest of the users towards the API Operator. > Following are some of the noticed issues from the initial discussion[2]. > >1. DockerHub account configuration (Kaniko job uses this configuration >to push built runtime image of api microgateway). > - Users have to go through *multiple editing* in configuration file > - Users have to *encode* credentials with base64 >2. Download multiple distributions. > - *API Operator* distribution[3] > - CLI tool: *apictl* distribution[4] > > > *Solution:* > Enable the *apictl* tool itself to install *API Operator* and configure > docker registry configurations and credentials. > > *Proposed commands:* > apictl install operator > Shall we give this a specific name (eg: apictl install *api-operator*). If we come up with more operators, we need to figure out a way to identify the operators. > After executing the above command, it would prompt the user to enter the > following > >1. Docker registry url (if the user is using a private docker >registry, has to provide the value. Otherwise just press "return") >2. Docker registry repository name >3. Docker username >4. Docker password > > Once these things are provided, *apictl* will create a *kubernetes-secret* > to be used by the Kaniko job. Finally, everything is configured and the > operator is up and running. > As of now, we are giving 3 option when configuring the API Operator. 1. Via default resources hosted in GitHub. - In this scenario, user would not have to provide any arguments to the above command (apictl install api-operator). The *apictl* will apply the k8s resources hosted in GitHub in the k8s cluster, 2. Ponting to a location file system - User can download the api-operagtor distribution and make configuration changes as the user needs. Once the k8s resources are configured user can execute the above command pointing to the configuration located in the file system with "-f" flag. - eg: *apictl install api-operator -f * 3. Hosting artefacts within the local network. - In some environments, internet access might not be available. In that case, they can host these artefacts in their local network after doing configuration changes. - We can use the same command as above, pointing to the api-operator distribution's config directory hosted within the local network. - eg: *apictl install api-operator -f * [1] https://operatorhub.io/operator/api-operator > [2] Attached PDF > [3] https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.1 > [4] https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.1 > > Thanks > Best Regards > > *Renuka Fernando* | Software Engineer | WSO2 Inc. > (m) +9476 6678 752 | Email: ren...@wso2.com > <http://wso2.com/signature> > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] API Operator for Kubernetes 1.0.0 Released!
*API Operator for Kubernetes 1.0.0 Released!* As microservices are increasingly being deployed on Kubernetes, the need to expose these microservices as well documented, easy to consume, managed APIs is becoming important to develop great applications. The API operator for Kubernetes makes APIs a first-class citizen in the Kubernetes ecosystem. Similar to deploying microservices, you can now use this operator to deploy APIs for individual microservices or compose several microservices into individual APIs. With this users will be able to expose their microservice as managed API in Kubernetes environment without any additional work. *Distribution & Documentation* The distribution of the API Operator can be found in API Operator GitHub <https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.0> repository. Quick Start Guide <https://github.com/wso2/k8s-apim-operator/blob/v1.0.0/docs/GettingStarted/quick-start-guide.md> Documentation <https://github.com/wso2/k8s-apim-operator/tree/v1.0.0/docs> Bug Fixes And Improvements in API Operator 1.0.0 Fixed issues <https://github.com/wso2/k8s-apim-operator/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+label%3A1.0.0> Known Issues All the open issues pertaining to WSO2 Kubernetes APIM Operator are reported at GitHub <https://github.com/wso2/k8s-apim-operator/issues> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: d...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> *User Forum:* StackOverflow <https://stackoverflow.com/questions/tagged/wso2-am> *WSO2 APIM Slack <https://wso2-apim.slack.com/>: *Join <https://join.slack.com/t/wso2-apim/shared_invite/enQtNzEzMzk5Njc5MzM0LTgwODI3NmQ1MjI0ZDQyMGNmZGI4ZjdkZmI1ZWZmMjNkY2E0NmY3ZmExYjkxYThjNzNkOTU2NWJmYzM4YzZiOWU?src=sidebar> Reporting Issues We encourage you to report issues, improvements and feature requests regarding API Operator through GitHub <https://github.com/wso2/k8s-apim-operator/issues> *Important:* And please be advised that security issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting the security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 API Manager Tooling 3.0.0 is Released!
*The WSO2 API Manager team is pleased to announce the release of version 3.0.0 of API Manager Tooling.* The WSO2 API Manager tooling provides the capability to import and export APIs and Applications across multiple environments seamlessly. Hence it provides greater flexibility to create CI/CD pipelines for APIs and applications. Apart from API and application migration, it supports for Kubernetes API operator to deploy and manage APIs in the Kubernetes cluster by reducing additional overheads for the DevOps. *Distributions & Documentation* API Manager Tooling Distribution <https://wso2.com/api-management/tooling/> API Manager Tooling Documentation <https://apim.docs.wso2.com/en/latest/Learn/CICDPipeline/initializing-projects-using-the-cli-tool/> Bug Fixes And Improvements in API Manager Tooling 3.0.0 Fixed issues <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aissue+is%3Aclosed+label%3A3.0.0> Known Issues All the open issues pertaining to WSO2 API Manager Tooling are reported at GitHub <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aopen+is%3Aissue> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: d...@wso2.org | Subscribe | Mail Archive - User List: u...@wso2.org | Subscribe | Mail Archive *User Forum:* StackOverflow <https://stackoverflow.com/questions/tagged/wso2-am> *WSO2 APIM Slack <https://wso2-apim.slack.com/>: *Join <https://join.slack.com/t/wso2-apim/shared_invite/enQtNzEzMzk5Njc5MzM0LTgwODI3NmQ1MjI0ZDQyMGNmZGI4ZjdkZmI1ZWZmMjNkY2E0NmY3ZmExYjkxYThjNzNkOTU2NWJmYzM4YzZiOWU?src=sidebar> Reporting Issues We encourage you to report issues, improvements and feature requests regarding WSO2 API Manager Tooling through tooling GitHub repository <https://github.com/wso2/product-apim-tooling/issues/new>. *Important:* And please be advised that security issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting the security issues. *-- The WSO2 API Manager Team --* *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 Kubernetes APIM Operator v1.0.0-Beta is Released!
*The WSO2 API Manager team is pleased to announce the release of version 1.0.0-Beta of Kubernetes APIM Operator.* WSO2 API Manager is a full lifecycle API Management solution with monetization and policy enforcement. WSO2 API Microgateway is a cloud-native, developer-centric and decentralized API gateway for microservices. Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications. The intention of this project is to provide cloud-native full API management by seamless integration with Kubernetes. With this native API Management support on K8s, this targets to improve the developer/devOps experience. *Distribution & Documentation* WSO2 Kubernetes APIM Operator Distribution <https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.0-beta> Documentation <https://github.com/wso2/k8s-apim-operator/blob/v1.0.0-beta/README.md> Bug Fixes And Improvements in WSO2 APIM Kubernetes Operator v1.0.0-Beta Fixed issues <https://github.com/wso2/k8s-apim-operator/issues?q=label%3Av1.0.0-beta+is%3Aclosed> Known Issues All the open issues pertaining to WSO2 Kubernetes APIM Operator are reported at GitHub <https://github.com/wso2/k8s-apim-operator/issues> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: d...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 Kubernetes APIM Operator through k8s-apim-operator <https://github.com/wso2/k8s-apim-operator/issues>. Please be advised that the *s*ecurity issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the security vulnerability reporting guide <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] WSO2 API Manager Tooling v3.0.0-Alpha is Released!
*The WSO2 API Manager team is pleased to announce the release of version 3.0.0-Alpha of API Manager Tooling.* Major improvements include supporting token generation for APIs for testing purposes. Also, it includes support for Kubernetes APIM operator to deploy and manage APIs in the Kubernetes cluster. Further, APIM CLI supports API updates and exporting applications with consumer key and secrets. Also, this release provides greater flexibility to create CI/CD pipelines for APIs. *Distributions & Documentation* APIM CLI Distributions <https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-alpha> APIM CLI Documentations <https://github.com/wso2/product-apim-tooling/blob/v3.0.0-alpha/import-export-cli/docs/apimcli.md> Bug Fixes And Improvements in API Manager Tooling v3.0.0-Alpha Fixed issues <https://github.com/wso2/product-apim-tooling/labels/apim-v3-alpha> Known Issues All the open issues pertaining to WSO2 API Manager Tooling are reported at GitHub <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aopen+is%3Aissue> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: d...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Tooling through the public API Manager Tooling Git Repo. <https://github.com/wso2/product-apim-tooling/issues> If it is a security issue then it must be reported to secur...@wso2.com, not as a GitHub issue. We strongly advise following the security vulnerability reporting guide <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [API Manager] Improve APIM CLI to generate a token for an API
Hi Harsha, This is already handled. Once the APIs are subscribed to the application, all the scopes of the APIs subscribed to the application are retrieved. Then scopes will be passed when generating the access token. Another concern we need to handle is pointing the endpoints to the apimcli tool. Because APIM 3.0.0 is shipped with rest API v0.14 and the v1. Currently, the apimcli tool is compatible with v0.14. Hence I've also carried out the implementation based on v0.14. Thanks, DinushaD On Fri, Sep 13, 2019 at 11:08 AM Harsha Kumara wrote: > It should be fine. What happen if API resources protect with scopes? May > be request all the scopes in the API with the request? > > On Thu, Sep 12, 2019 at 11:56 PM Dinusha Dissanayake > wrote: > >> Hi Harsha, >> >> We are generating tokens using the client credentials grant type. Since >> this is only for testing purposes, we do not need to support multiple grant >> types. do we? >> >> >> On Thu, Sep 12, 2019 at 5:51 PM Harsha Kumara wrote: >> >>> @Dinusha Dissanayake Are we generating a client >>> credentials token or pass grant type based token? >>> >>> On Wed, Sep 4, 2019 at 10:31 AM Dinusha Dissanayake >>> wrote: >>> >>>> Hi Dushan, >>>> >>>> If we make it optional, users will use that to create applications and >>>> generate keys as they desire, which would again deviate the original >>>> purpose. Hence IMO I believe it is enough to limited to a single >>>> application as this is only for testing purposes. >>>> >>>> Thanks, >>>> DinushaD >>>> >>>> On Wed, Sep 4, 2019 at 10:04 AM Dushan Silva wrote: >>>> >>>>> I agree with nuwan on this we do not need to pass the application as >>>>> it would defeat the purpose of this feature in the first place. However we >>>>> can provide the application name as an *optional* parameter, if the >>>>> user has already created an application using the rest api, he can use >>>>> that >>>>> name using the CLI. WDYT? >>>>> >>>>> On Mon, Sep 2, 2019 at 5:20 PM Nuwan Dias wrote: >>>>> >>>>>> I think we should look back at the intention of this command. The two >>>>>> main objectives of the key-gen commands are as below. >>>>>> >>>>>> 1) For someone using the CLI to create, deploy and test APIs without >>>>>> leaving the terminal itself. >>>>>> 2) For CI/CD tools to be able to perform automated tests before >>>>>> promoting APIs to upper environments. >>>>>> >>>>>> Given the above two objectives, any input required other than the API >>>>>> name and version itself would jeopardise the purpose of this command. A >>>>>> CI/CD tool will anyway not be able to provide an application name, so >>>>>> that's out of the question I guess. If a human being who wants to test >>>>>> the >>>>>> API is requested to input the App name, that means that person has to >>>>>> login >>>>>> to the store and have awareness about an application, subscription, etc. >>>>>> If >>>>>> that person has access to the store, why would he/she need to generate >>>>>> keys >>>>>> from the CLI itself? The store already provides a key and also a cURL >>>>>> command to get a key using any preferred grant type anyway. So if we >>>>>> assume >>>>>> a person has to login to the store first to create or get info about an >>>>>> existing app, I see no further use of him/her to be using the key-gen >>>>>> command on the CLI. >>>>>> >>>>>> Thanks, >>>>>> NuwanD. >>>>>> >>>>>> On Mon, Sep 2, 2019 at 3:41 PM Chamila Adhikarinayake < >>>>>> chami...@wso2.com> wrote: >>>>>> >>>>>>> Hi Pubudu, >>>>>>> Any reason for subscribing to the default application? I think we >>>>>>> should pass the application name as a parameter instead of subscribing >>>>>>> to a >>>>>>> default application. >>>>>>> >>>>>>> On Mon, Sep 2, 2019 at 12:19 PM Pubudu Gunatilaka >>>>>>> wrote: >>>>>>> >>>>>>>&g
Re: [Architecture] [API Manager] Improve APIM CLI to generate a token for an API
Hi Harsha, We are generating tokens using the client credentials grant type. Since this is only for testing purposes, we do not need to support multiple grant types. do we? On Thu, Sep 12, 2019 at 5:51 PM Harsha Kumara wrote: > @Dinusha Dissanayake Are we generating a client > credentials token or pass grant type based token? > > On Wed, Sep 4, 2019 at 10:31 AM Dinusha Dissanayake > wrote: > >> Hi Dushan, >> >> If we make it optional, users will use that to create applications and >> generate keys as they desire, which would again deviate the original >> purpose. Hence IMO I believe it is enough to limited to a single >> application as this is only for testing purposes. >> >> Thanks, >> DinushaD >> >> On Wed, Sep 4, 2019 at 10:04 AM Dushan Silva wrote: >> >>> I agree with nuwan on this we do not need to pass the application as it >>> would defeat the purpose of this feature in the first place. However we can >>> provide the application name as an *optional* parameter, if the user >>> has already created an application using the rest api, he can use that name >>> using the CLI. WDYT? >>> >>> On Mon, Sep 2, 2019 at 5:20 PM Nuwan Dias wrote: >>> >>>> I think we should look back at the intention of this command. The two >>>> main objectives of the key-gen commands are as below. >>>> >>>> 1) For someone using the CLI to create, deploy and test APIs without >>>> leaving the terminal itself. >>>> 2) For CI/CD tools to be able to perform automated tests before >>>> promoting APIs to upper environments. >>>> >>>> Given the above two objectives, any input required other than the API >>>> name and version itself would jeopardise the purpose of this command. A >>>> CI/CD tool will anyway not be able to provide an application name, so >>>> that's out of the question I guess. If a human being who wants to test the >>>> API is requested to input the App name, that means that person has to login >>>> to the store and have awareness about an application, subscription, etc. If >>>> that person has access to the store, why would he/she need to generate keys >>>> from the CLI itself? The store already provides a key and also a cURL >>>> command to get a key using any preferred grant type anyway. So if we assume >>>> a person has to login to the store first to create or get info about an >>>> existing app, I see no further use of him/her to be using the key-gen >>>> command on the CLI. >>>> >>>> Thanks, >>>> NuwanD. >>>> >>>> On Mon, Sep 2, 2019 at 3:41 PM Chamila Adhikarinayake < >>>> chami...@wso2.com> wrote: >>>> >>>>> Hi Pubudu, >>>>> Any reason for subscribing to the default application? I think we >>>>> should pass the application name as a parameter instead of subscribing to >>>>> a >>>>> default application. >>>>> >>>>> On Mon, Sep 2, 2019 at 12:19 PM Pubudu Gunatilaka >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> With the latest improvements to the APIMCLI, users are able to >>>>>> publish the API in published state and it allows Store users to discover >>>>>> the API in the developer portal. Basically, to invoke the API, he has to >>>>>> obtain an access token and has to follow the following approach. >>>>>> >>>>>> 1. Log in to the Store >>>>>> 2. Subscribe to an API >>>>>> 3. Generate an access token >>>>>> >>>>>> For any user, he has to use the above approach or use the REST APIs >>>>>> and generate the token. >>>>>> >>>>>> We have improved the CI/CD pipeline approach with APIMCLI and we can >>>>>> further enhance this by allowing APIMCLI to generate an access token. So >>>>>> the CI/CD pipeline can be improved to run a test suite with the generated >>>>>> access token from the APIMCLI. >>>>>> >>>>>> Suggested CLI command: >>>>>> >>>>>> *apimcli get keys -n TwitterAPI -v 1.0.0 -e dev --provider admin* >>>>>> >>>>>> This command does the following. >>>>>> >>>>>> 1. Subscribe the given API to the Default Application if it not >>
Re: [Architecture] [Dev] [DEV] [VOTE] Release WSO2 API Microgateway 3.0.1 RC3
>>>>>>> >>>>>>> Documentation: https://docs.wso2.com/display/MG301/ >>>>>>> >>>>>>> Best Regards, >>>>>>> WSO2 API Manager Team >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Rajith Roshan* | Associate Technical Lead | WSO2 Inc. >>>>>> (m) +94-717-064-214 | (e) raji...@wso2.com >>>>>> >>>>>> <https://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Praminda Jayawardana* | Senior Software Engineer | WSO2 Inc. >>>>> (m) +94 (0) 716 590918 | (e) prami...@wso2.com >>>>> GET INTEGRATION AGILE >>>>> Integration Agility for Digitally Driven Business >>>>> ___ >>>>> Dev mailing list >>>>> d...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> >>>> *Menaka Jayawardena* >>>> Senior Software Engineer | WSO2 Inc. >>>> +94 71 350 5470 | +94 76 717 2511 | men...@wso2.com >>>> >>>> <https://wso2.com/signature> >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> >>> >>> -- >>> Malintha Amarasinghe >>> *WSO2, Inc. - lean | enterprise | middleware* >>> http://wso2.com/ >>> >>> Mobile : +94 712383306 >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Hasunie Adikari* >> Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> blog http://hasuniea.blogspot.com | https://medium.com/@Hasunie/ >> Mobile:+94713095876 >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc. > +94 710 618 178 > GET INTEGRATION AGILE > Integration Agility for Digitally Driven Business > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3
>> Tested the following. >>>>>>>> >>>>>>>> Basic API creation by creator role >>>>>>>> Publishing by publisher role >>>>>>>> User sign up >>>>>>>> Creation and invocation of SOAP APIs >>>>>>>> Microgateway VM mode >>>>>>>> Microgateway docker mode >>>>>>>> >>>>>>>> [+] Stable - go ahead and release >>>>>>>> >>>>>>>> Thanks, >>>>>>>> NuwanD. >>>>>>>> >>>>>>>> On Sat, Sep 15, 2018 at 10:34 AM Chamila Adhikarinayake < >>>>>>>> chami...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Microgateway RC3 can be found in >>>>>>>>> https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc3 >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Chamila >>>>>>>>> >>>>>>>>> On Sat, Sep 15, 2018 at 7:04 AM, Chamila Adhikarinayake < >>>>>>>>> chami...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi All, >>>>>>>>>> >>>>>>>>>> We are pleased to announce the third release candidate of >>>>>>>>>> WSO2 API Manager 2.6.0. >>>>>>>>>> >>>>>>>>>> This release fixes the following issues. >>>>>>>>>> >>>>>>>>>> Fixes : carbon-apimgt >>>>>>>>>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15+-label%3A%22APIM+3.0.0%22> >>>>>>>>>> Fixes : product-apim >>>>>>>>>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15+-label%3A%223.0.0%22> >>>>>>>>>> Fixes : analytics-apim >>>>>>>>>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15> >>>>>>>>>> Fixes : product-microgateway >>>>>>>>>> <https://github.com/wso2/product-microgateway/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15> >>>>>>>>>> >>>>>>>>>> Source and Distribution, >>>>>>>>>>- Runtime : >>>>>>>>>> https://github.com/wso2/product-apim/releases/tag/v2.6.0-rc3 >>>>>>>>>>- Analytics : >>>>>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v2.6.0-rc3 >>>>>>>>>>- Tooling : >>>>>>>>>> https://github.com/wso2/devstudio-tooling-apim/releases/tag/v2.6.0-rc1 >>>>>>>>>>- Microgateway : >>>>>>>>>> https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc2 >>>>>>>>>> >>>>>>>>>> Please download, test the product and vote. >>>>>>>>>> >>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> ~ WSO2 API Manager Team ~ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> Chamila Adhikarinayake >>>>>>>>>> Associate Technical Lead >>>>>>>>>> WSO2, Inc. >>>>>>>>>> Mobile - +94712346437 >>>>>>>>>> Email - chami...@wso2.com >>>>>>>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Regards, >>>>>>>>> Chamila Adhikarinayake >>>>>>>>> Associate Technical Lead >>>>>>>>> WSO2, Inc. >>>>>>>>> Mobile - +94712346437 >>>>>>>>> Email - chami...@wso2.com >>>>>>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Nuwan Dias* | Director | WSO2 Inc. >>>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>>>>>>> [image: Signature.jpg] >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> d...@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Sanjeewa Malalgoda* >>>>>>> Software Architect | Associate Director, Engineering WSO2 Inc. >>>>>>> (m) +94 712933253 | (e) sanje...@wso2.com >>>>>>> >>>>>>> GET INTEGRATION AGILE <https://wso2.com/signature> >>>>>>> Integration Agility for Digitally Driven Business >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> d...@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rajith Roshan >>>>>> Senior Software Engineer, WSO2 Inc. >>>>>> Mobile: +94-7 <%2B94-71-554-8430>17-064-214 >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> Chamila Adhikarinayake >>>>> Associate Technical Lead >>>>> WSO2, Inc. >>>>> Mobile - +94712346437 >>>>> Email - chami...@wso2.com >>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>> ___ >>>>> Dev mailing list >>>>> d...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards >>>> >>>> *Chaminda Jayawardena* >>>> WSO2 Inc. - http://wso2.com >>>> +94-77-7725234 >>>> >>>> ___ >>>> Dev mailing list >>>> d...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Naduni Pamudika* >>> Software Engineer | WSO2 >>> >>> Mobile: +94 719 143658 <+94%2071%20914%203658> >>> LinkedIn: https://lk.linkedin.com/in/naduni-pamudika >>> Blog: https://medium.com/@naduni_pamudika >>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> >> >> -- >> >> *Tharindu Dharmarathna*Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: *+94779109091* >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > Vithursa Mahendrarajah > Software Engineer > WSO2 Inc. - http ://wso2.com > Mobile : +947*66695643* <+94%2077%20819%201300> > > > * <http://wso2.com/signature> <http://wso2.com/signature> > <http://wso2.com/signature>* > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Moving to a user configurable model to set threshold values for APIM analytics instead of percentile values
Hi Silmy, Hi all, > > According to the current implementation of APIM Analytics , we use > percentile values to find out certain threshold values (eg:- Abnormal > request count) . Since generating alerts using percentile values creates > lots of complexity to the users of the alert, it was decided to move > towards a user configurable system where admins and subscribers can set > those threshold values directly. > > *Note* > >- There will not be any default values for those thresholds. >- The alerts will not be generated to the particualr API or >application untill the admins or subscribers set a value for those >thresholds. > > Two possible ways could be identified to let the admins and subscribers to > configure these values, > >1. Let the admins or subcribers set those values in APIM side and >publish it to SP as a stream. A siddhi app can be written to listen to the >stream an store it in database >2. Let the admins or subscriber set a value at SP dashboard itself >using a dashboard widget > > If we are letting subscribers to set the throshold values, the subscriber has to login to SP ? If so, it would reduce the user experience IMO. Can you please explain how the flow goes for subscribers when setting these values? -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM][Micro-Gateway][Analytics] Analytics for Micro-gateway
t;> >>>>>>>>> Thanks & Regards, >>>>>>>>> >>>>>>>>> *Fazlan Nazeem* >>>>>>>>> Senior Software Engineer >>>>>>>>> WSO2 Inc >>>>>>>>> Mobile : +94772338839 >>>>>>>>> fazl...@wso2.com >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Tishan Dahanayakage >>>>>>>> Associate Technical Lead >>>>>>>> WSO2, Inc. >>>>>>>> Mobile:+94 716481328 >>>>>>>> >>>>>>>> Disclaimer: This communication may contain privileged or other >>>>>>>> confidential information and is intended exclusively for the >>>>>>>> addressee/s. >>>>>>>> If you are not the intended recipient/s, or believe that you may have >>>>>>>> received this communication in error, please reply to the sender >>>>>>>> indicating >>>>>>>> that fact and delete the copy you received and in addition, you should >>>>>>>> not >>>>>>>> print, copy, re-transmit, disseminate, or otherwise use the information >>>>>>>> contained in this communication. Internet communications cannot be >>>>>>>> guaranteed to be timely, secure, error or virus-free. The sender does >>>>>>>> not >>>>>>>> accept liability for any errors or omissions. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Tishan Dahanayakage >>>>>>> Associate Technical Lead >>>>>>> WSO2, Inc. >>>>>>> Mobile:+94 716481328 >>>>>>> >>>>>>> Disclaimer: This communication may contain privileged or other >>>>>>> confidential information and is intended exclusively for the >>>>>>> addressee/s. >>>>>>> If you are not the intended recipient/s, or believe that you may have >>>>>>> received this communication in error, please reply to the sender >>>>>>> indicating >>>>>>> that fact and delete the copy you received and in addition, you should >>>>>>> not >>>>>>> print, copy, re-transmit, disseminate, or otherwise use the information >>>>>>> contained in this communication. Internet communications cannot be >>>>>>> guaranteed to be timely, secure, error or virus-free. The sender does >>>>>>> not >>>>>>> accept liability for any errors or omissions. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Dinusha Dissanayake >>>>>> Software Engineer >>>>>> WSO2 Inc >>>>>> Mobile: +94712939439 >>>>>> <https://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Tishan Dahanayakage >>>>> Associate Technical Lead >>>>> WSO2, Inc. >>>>> Mobile:+94 716481328 >>>>> >>>>> Disclaimer: This communication may contain privileged or other >>>>> confidential information and is intended exclusively for the addressee/s. >>>>> If you are not the intended recipient/s, or believe that you may have >>>>> received this communication in error, please reply to the sender >>>>> indicating >>>>> that fact and delete the copy you received and in addition, you should not >>>>> print, copy, re-transmit, disseminate, or otherwise use the information >>>>> contained in this communication. Internet communications cannot be >>>>> guaranteed to be timely, secure, error or virus-free. The sender does not >>>>> accept liability for any errors or omissions. >>>>> >>>> >>>> >>>> >>>> -- >>>> Dinusha Dissanayake >>>> Software Engineer >>>> WSO2 Inc >>>> Mobile: +94712939439 >>>> <https://wso2.com/signature> >>>> >>> >> >> -- >> Nuwan Dias >> >> Software Architect - WSO2, Inc. http://wso2.com >> email : nuw...@wso2.com >> Phone : +94 777 775 729 >> > > > -- > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94 712933253 > > <http://sanjeewamalalgoda.blogspot.com/>blog > :http://sanjeewamalalgoda.blogspot.com/ > <http://sanjeewamalalgoda.blogspot.com/> > > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM][Micro-Gateway][Analytics] Analytics for Micro-gateway
Hi Tishan, > >>> One more thing. Can't we just save these zip files to file system rather >>> than stressing STATS_DB. We use STATS_DB mainly to store end analytics data >>> which is used by presentation layer(Dashboards). WDYT? >>> >> This would be problematic in HA deployment. If we keep them in the file >> system and if a node goes down, we won't be able to retrieve the event >> data in files in that node. >> > That we can solve by publishing to both DAS nodes from GW. Even earlier I > was discussing with Fazlan to avoid adding file to DB by using file tail > adaptor but later reverted due to zip files. But given that we are now > using custom adaptor we can use files :) > If we publish to both DAS nodes, then the files would be available in both nodes. When event publishing is happening by reading those files, the same file will be processed from both the nodes right? :) Then the same events will be accumulated twice as I see. > > /Tishan > >> >> >> > >>> >> /Tishan >>> >>> On Fri, Jun 29, 2018 at 2:42 PM, Tishan Dahanayakage >>> wrote: >>> >>>> Fazlan, >>>> >>>> On Fri, Jun 29, 2018 at 2:17 PM, Fazlan Nazeem >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> At the moment, analytics for microgateway is supported via a JAX-RS >>>>> web app and a custom component which are deployed in APIM publisher node. >>>>> The component was responsible for publishing the analytics data persisted >>>>> in a DB table to the Analytics server via thrift. As an improvement for >>>>> this, we have planned to move the web app to Analytics server and process >>>>> the events within itself which will remove the overhead of publishing data >>>>> via thrift. The micro-gateways will then upload the zip files >>>>> with analytics data directly to the analytics server so that we can >>>>> eliminate an unnecessary network hop. >>>>> >>>>> For this, we have developed a working prototype which follows the >>>>> following design. >>>>> >>>>> [image: micro-analytics.jpg] >>>>> >>>>> With the above design, a user has to follow the following steps to >>>>> setup analytics in APIM Analytics server for micro-gateway. >>>>> >>>>> 1) Deploy the JAX-RS web app. >>>>> 2) Deploy the custom event receiver jar file to dropins. >>>>> 3) Deploy the CAPP with the custom event receivers for required >>>>> streams. >>>>> 4) Create a table in STATS_DB to persist the zip file >>>>> 5) Start analytics server with a set of system properties which will >>>>> configure the Timer task intervals etc. >>>>> >>>> Can't we have these as parameters of the custom receiver so that we >>>> can have them pre-configured offloading tasks from user. Or else set >>>> reasonable defaults. And I believe timer tasks are started by Custom Event >>>> Receiver. >>>> >>>> /Tishan >>>> >>>> >>>>> >>>>> The micro-gateway needs to be configured with the JAX-RS web app's URI >>>>> so that it can periodically upload files with analytics data to the APIM >>>>> Analytics server. >>>>> >>>>> Any feedback? >>>>> >>>>> >>>>> Thanks & Regards, >>>>> >>>>> *Fazlan Nazeem* >>>>> Senior Software Engineer >>>>> WSO2 Inc >>>>> Mobile : +94772338839 >>>>> fazl...@wso2.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Tishan Dahanayakage >>>> Associate Technical Lead >>>> WSO2, Inc. >>>> Mobile:+94 716481328 >>>> >>>> Disclaimer: This communication may contain privileged or other >>>> confidential information and is intended exclusively for the addressee/s. >>>> If you are not the intended recipient/s, or believe that you may have >>>> received this communication in error, please reply to the sender indicating >>>> that fact and delete the copy you received and in addition, you should not >>>> print, copy, re-transmit, disseminate, or otherwise use the information >>>> contained in this communication. Internet communications cannot be >>&
Re: [Architecture] [APIM][Micro-Gateway][Analytics] Analytics for Micro-gateway
Hi Fazlan, Please find my concerns below. > > > With the above design, a user has to follow the following steps to setup > analytics in APIM Analytics server for micro-gateway. > > 1) Deploy the JAX-RS web app. > 2) Deploy the custom event receiver jar file to dropins. > 3) Deploy the CAPP with the custom event receivers for required streams. > 4) Create a table in STATS_DB to persist the zip file > 5) Start analytics server with a set of system properties which will > configure the Timer task intervals etc. > I believe we have to provide data publishing time interval and clean up tasks interval here right? Will there be any additional fields? > > The micro-gateway needs to be configured with the JAX-RS web app's URI so > that it can periodically upload files with analytics data to the APIM > Analytics server. > > Any feedback? > > > Thanks & Regards, > > *Fazlan Nazeem* > Senior Software Engineer > WSO2 Inc > Mobile : +94772338839 > fazl...@wso2.com > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC4
gt;>>>> WSO2 API Manager Team. >>>>> >>>>> -- >>>>> Chamin Dias >>>>> Mobile : 0716097455 >>>>> Email : cham...@wso2.com >>>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> d...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Krishan Wijesena* >>>> Software Engineer | WSO2 >>>> >>>> Email : krish...@wso2.com >>>> Mobile : +94776219923 >>>> WSO2 Inc : http://wso2.com >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> >>> >>> >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : cham...@wso2.com >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks & Regards, >> >> *Chamalee De Silva* >> Senior Software Engineer >> *WS**O2* Inc. :http://wso2.com/ >> >> Office :- *+94 11 2145345 <%2B94%2011%202145345>* >> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* >> >> ___ >> Dev mailing list >> d...@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Tharika Madurapperuma* > Software Engineer | WSO2, Inc. > > Email : thar...@wso2.com > Mobile : +94777875624 > Web : http://wso2.com > > <http://wso2.com/signature> > > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Analytics Filter for Microgateway
Hi Chamila
We are handling it through the code.
.dat will be compressed according to a configured time interval (say per
every 10 mins). Then the zip will be uploaded to endpoint as mentioned
above. If it is a success, then the zip will be deleted.
Table clean up task will be running and cleaning the DB periodically.
@Fazlan is working on that I think.
On Thu, Jun 21, 2018 at 2:31 PM, Chamila Adhikarinayake
wrote:
> Hi Dinusha,
>
> How do we handle the cleanup tasks related to this feature? (Deleting .dat
> files, removing entries from AM_USAGE_UPLOADED_FILES) . These tables will
> grow with time (same as the auth token table issue currently we have in
> APIM/IS). Are we handling it through code (remove entries/files after
> reading or similar method) or running a separate script to remove them?.
>
>
> Chamila.
>
>
> On Wed, Jun 20, 2018 at 11:29 AM, Dinusha Dissanayake
> wrote:
>
>> Hi Sinthuja,
>>
>> What we are trying to do here is, persist the events coming from
>> micro-gateway so that events would not be lost when publishing them to
>> analytics.
>> Microgateway should be able to run on its own. If analytics server is not
>> present at the moment we are invoking APIs in microgateway, there should be
>> a way to persist those data. Hence we are writing them into a file so that
>> we can publish them into analytics later.
>>
>> This is similar approach what we have done in APIM 2.2.0 and in cloud
>> with on premises gateway concept.
>>
>> On Fri, Jun 8, 2018 at 5:34 PM, Sinthuja Rajendran
>> wrote:
>>
>>> Hi Dinusha,
>>>
>>> Can you explain what is the problem we are trying to solve with this
>>> approach? I'm not clear based on our problem statement or use case based on
>>> the explanation given above.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Tue, Jun 5, 2018 at 10:35 AM Dinusha Dissanayake
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We've been working on analytics filter for APIM 2.5 microgateway.
>>>> Following is the design we came up with.
>>>>
>>>> *1. Filtering the event data and writing them to a file.*
>>>>
>>>>
>>>> From the request stream, the relevant fields will be extracted and
>>>> requestDTO will be populated using those attributes.
>>>> EventDTO consist of streamID, timestamp, metadata, correlation data and
>>>> payload data.
>>>> EventDTO can be populated using requestDTO.
>>>>
>>>> Likewise when the response filters are available, we can extract the
>>>> necessary attributes and fill ExecutionTimeDTO and ResponseDTO. Then the
>>>> eventDTO can be populated corresponding to response related attributes.
>>>>
>>>> Once EventDTO is populated, we publish those events in to event stream.
>>>> A method to write those events to a file has been subscribed to the
>>>> event stream at the gateway initialization process.
>>>> Hence whenever a events stream gets an event, it will write that event
>>>> to the file we are defining.
>>>>
>>>>
>>>> *2. Event publishing from files to analytics server.*
>>>>
>>>> Files will be written with .dat extension.
>>>> For example say "api-usage-data.dat".
>>>>
>>>> In APIM v2.2 micro gateway, this file would rotate if the file size
>>>> exceeds 12mb or after a specific time interval. These values could be set
>>>> as configurable values.
>>>> Rolled file will be compressed with the timestamp.
>>>> eg: *api-usage-data.{timstamp}.zip*
>>>> This would reduce 12mb file into (approximately) 4kb file.
>>>>
>>>> Then this zip(s) will be uploaded and persisted in a DB. This will be
>>>> done using ballerina tasks(to make it happen periodically).
>>>> Then the relevant entries (files) will be read from the DB and populate
>>>> the events by reading line by line of that files. Then those events will be
>>>> published to the analytics server using existing data publisher.
>>>>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>> DinushaD
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dinusha Dissanayake
>>>> Software Engineer
>>>> WSO2 Inc
>>>> Mobile: +94712939439
>>>> <https://wso2.com/signature>
>>>> ______
Re: [Architecture] Analytics Filter for Microgateway
Hi Sinthuja,
What we are trying to do here is, persist the events coming from
micro-gateway so that events would not be lost when publishing them to
analytics.
Microgateway should be able to run on its own. If analytics server is not
present at the moment we are invoking APIs in microgateway, there should be
a way to persist those data. Hence we are writing them into a file so that
we can publish them into analytics later.
This is similar approach what we have done in APIM 2.2.0 and in cloud with
on premises gateway concept.
On Fri, Jun 8, 2018 at 5:34 PM, Sinthuja Rajendran
wrote:
> Hi Dinusha,
>
> Can you explain what is the problem we are trying to solve with this
> approach? I'm not clear based on our problem statement or use case based on
> the explanation given above.
>
> Thanks,
> Sinthuja.
>
> On Tue, Jun 5, 2018 at 10:35 AM Dinusha Dissanayake
> wrote:
>
>> Hi all,
>>
>> We've been working on analytics filter for APIM 2.5 microgateway.
>> Following is the design we came up with.
>>
>> *1. Filtering the event data and writing them to a file.*
>>
>>
>> From the request stream, the relevant fields will be extracted and
>> requestDTO will be populated using those attributes.
>> EventDTO consist of streamID, timestamp, metadata, correlation data and
>> payload data.
>> EventDTO can be populated using requestDTO.
>>
>> Likewise when the response filters are available, we can extract the
>> necessary attributes and fill ExecutionTimeDTO and ResponseDTO. Then the
>> eventDTO can be populated corresponding to response related attributes.
>>
>> Once EventDTO is populated, we publish those events in to event stream.
>> A method to write those events to a file has been subscribed to the event
>> stream at the gateway initialization process.
>> Hence whenever a events stream gets an event, it will write that event to
>> the file we are defining.
>>
>>
>> *2. Event publishing from files to analytics server.*
>>
>> Files will be written with .dat extension.
>> For example say "api-usage-data.dat".
>>
>> In APIM v2.2 micro gateway, this file would rotate if the file size
>> exceeds 12mb or after a specific time interval. These values could be set
>> as configurable values.
>> Rolled file will be compressed with the timestamp.
>> eg: *api-usage-data.{timstamp}.zip*
>> This would reduce 12mb file into (approximately) 4kb file.
>>
>> Then this zip(s) will be uploaded and persisted in a DB. This will be
>> done using ballerina tasks(to make it happen periodically).
>> Then the relevant entries (files) will be read from the DB and populate
>> the events by reading line by line of that files. Then those events will be
>> published to the analytics server using existing data publisher.
>>
>>
>>
>>
>> Thanks,
>> DinushaD
>>
>>
>>
>>
>> --
>> Dinusha Dissanayake
>> Software Engineer
>> WSO2 Inc
>> Mobile: +94712939439
>> <https://wso2.com/signature>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> *Sinthuja Rajendran*
> Senior Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439
<https://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC3
gt;> WSO2 API Manager Team >>>>> >>>>> -- >>>>> Chamin Dias >>>>> Mobile : 0716097455 >>>>> Email : cham...@wso2.com >>>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>>> >>>>> >>>>> ___________ >>>>> Dev mailing list >>>>> d...@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> >>>> *Chamalee De Silva* >>>> Senior Software Engineer >>>> *WS**O2* Inc. :http://wso2.com/ >>>> >>>> Office :- *+94 11 2145345 <%2B94%2011%202145345>* >>>> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* >>>> >>>> >>> >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : cham...@wso2.com >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> >>> ___ >>> Dev mailing list >>> d...@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Vithursa Mahendrarajah >> Software Engineer >> WSO2 Inc. - http ://wso2.com >> Mobile : +947*66695643* <+94%2077%20819%201300> >> >> >> * <http://wso2.com/signature> <http://wso2.com/signature> >> <http://wso2.com/signature>* >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] APIM CLI simplify endpoint url configs
Hi Rukshan, Would we need to consider here the uploading endpoint of the analytics data files as well? Currently we are planing to include it in conf file. Thanks, DinushaD. On Mon, Jun 18, 2018 at 2:37 PM, Rukshan Premathunga wrote: > Hi, > > Here the additional details user need to provide as argument when setup > CLI tool. > >- Publisher Endpoint >- Registration Endpoint >- Admin Endpoint >- Token Endpoint >- Trust Store path >- Trust Store password > > > From them, Publisher, Registration, Admin and Token endpoints hostname > can be same. In such cases we can introduce a command argument --*URL. * If > URL is provided those urls are derived from that. In case if those apps are > in diffrent host, user need to edit them in default config file. Since this > a one time task and not likely to change much, i think it is fine. > Since all of these configs are mandatory we maintain some default values. > When user enter setup command, if those configs are not provided, prompt > user to enter values. If user didn't input any values default values are > use. Once all the setup execution is complete succesfully, user input save > to the config file and use next time onward. > > Here the few examples flow, ex:1 show *setup* command with all the > mandatory arguments and ex: 2 show without mandatory arguments. Hence > ex:2 prompt them from user. > > 1) > $ ./micro-gw *setup* --user amuser --*password* pass --label account -- > *url* https://localhost:9443/ --*path* /home/user/workspace --*truststore* > path/to/truststore --*truststorePass* password > $ Completed > > 2) > $ ./micro-gw *setup* --user amuser --*password* pass --*label* account -- > *path* /home/user/workspace > $ Enter *url* [ default https://localhost:9443/ ] : > https://apim.wso2.com:9443/ > $ Enter *truststore* [ default path/to/truststore ] : different/path/to/ > truststore > $ Enter *truststorePass* [ use default? ] : password > $ Completed > > > Any suggestions? > > Thanks and Regards > > > > On Mon, Jun 18, 2018 at 11:18 AM, Rukshan Premathunga > wrote: > >> I guess you are referring to the Microgateway CLI and not the APIM CLI. >> >> Yes. It should be Microgateway CLI >> >> >> On Mon, Jun 18, 2018 at 11:15 AM, Nuwan Dias wrote: >> >>> I guess you are referring to the Microgateway CLI and not the APIM CLI. >>> >>> On Mon, Jun 18, 2018 at 11:11 AM, Rukshan Premathunga >>> wrote: >>> >>>> Hi All, >>>> >>>> Currently CLI auto generate endpoints from defautl values and user have >>>> to edit it in order to work if endpoints are diffrent. As a solution we >>>> thought to provide urls as arguments for setup command. >>>> But here we have 4 endpoints(store, publisher, admin and token) to get >>>> as arguments. But making all of them as mandatory, user experience may get >>>> reduce, So we need to have a mechanism to derive them. >>>> >>>> One option is to use one host for apps in same node(store, pub, admin). >>>> If it is changed, provide the optional arguments to override them. >>>> >>>> So can you also share some idea please. >>>> >>>> Thanks and Regards >>>> -- >>>> >>>> Rukshan Chathuranga. >>>> WSO2, Inc. >>>> +94711822074 >>>> >>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Software Architect - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> Rukshan Chathuranga. >> Software Engineer. >> WSO2, Inc. >> +94711822074 >> > > > > -- > Rukshan Chathuranga. > Software Engineer. > WSO2, Inc. > +94711822074 > > ___ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Analytics Filter for Microgateway
Hi Pubudu,
This implementation from reader point onward is similar to what we already
have in APIM v 2.2.0.
1. So the reader resides in publisher ATM.
2. Yes. We are using AM_DB since there is a table already for this
AM_USAGE_UPLOADED_FILES so we do not need new work here.
3. Yes. This can be achieved via ballerina tasks. But we are making a
slight change here to upload file after each rotation.
ATM we are using file rotation based only on timstamps. (say if a file will
be rotated every 10 min )
After rotating the file, the then rotated file name would be added to a
stream which is containing file names.
We can subscriber the uploading method to this stream. So once this streams
gets an entry, it will call the uploading method and the corresponding file
will be uploaded.
Thanks,
DinushaD.
On Wed, Jun 6, 2018 at 5:52 AM, Pubudu Gunatilaka wrote:
> Hi Dinusha,
>
> I have few questions.
>
> 1. Where does the file reader reside? Is it in publisher node?
> 2. What is the database are we using here? AM_DB?
> 3. Why can't we run a Ballerina task or data publisher in the
> micro-gateway to publish events to the Analytics server?
>
> Thank you!
> Pubudu.
>
> On Mon, Jun 4, 2018 at 10:05 PM Dinusha Dissanayake
> wrote:
>
>> Hi all,
>>
>> We've been working on analytics filter for APIM 2.5 microgateway.
>> Following is the design we came up with.
>>
>> *1. Filtering the event data and writing them to a file.*
>>
>>
>> From the request stream, the relevant fields will be extracted and
>> requestDTO will be populated using those attributes.
>> EventDTO consist of streamID, timestamp, metadata, correlation data and
>> payload data.
>> EventDTO can be populated using requestDTO.
>>
>> Likewise when the response filters are available, we can extract the
>> necessary attributes and fill ExecutionTimeDTO and ResponseDTO. Then the
>> eventDTO can be populated corresponding to response related attributes.
>>
>> Once EventDTO is populated, we publish those events in to event stream.
>> A method to write those events to a file has been subscribed to the event
>> stream at the gateway initialization process.
>> Hence whenever a events stream gets an event, it will write that event to
>> the file we are defining.
>>
>>
>> *2. Event publishing from files to analytics server.*
>>
>> Files will be written with .dat extension.
>> For example say "api-usage-data.dat".
>>
>> In APIM v2.2 micro gateway, this file would rotate if the file size
>> exceeds 12mb or after a specific time interval. These values could be set
>> as configurable values.
>> Rolled file will be compressed with the timestamp.
>> eg: *api-usage-data.{timstamp}.zip*
>> This would reduce 12mb file into (approximately) 4kb file.
>>
>> Then this zip(s) will be uploaded and persisted in a DB. This will be
>> done using ballerina tasks(to make it happen periodically).
>> Then the relevant entries (files) will be read from the DB and populate
>> the events by reading line by line of that files. Then those events will be
>> published to the analytics server using existing data publisher.
>>
>>
>>
>>
>> Thanks,
>> DinushaD
>>
>>
>>
>>
>> --
>> Dinusha Dissanayake
>> Software Engineer
>> WSO2 Inc
>> Mobile: +94712939439
>> <https://wso2.com/signature>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439
<https://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Analytics Filter for Microgateway
Hi all,
We've been working on analytics filter for APIM 2.5 microgateway. Following
is the design we came up with.
*1. Filtering the event data and writing them to a file.*
>From the request stream, the relevant fields will be extracted and
requestDTO will be populated using those attributes.
EventDTO consist of streamID, timestamp, metadata, correlation data and
payload data.
EventDTO can be populated using requestDTO.
Likewise when the response filters are available, we can extract the
necessary attributes and fill ExecutionTimeDTO and ResponseDTO. Then the
eventDTO can be populated corresponding to response related attributes.
Once EventDTO is populated, we publish those events in to event stream.
A method to write those events to a file has been subscribed to the event
stream at the gateway initialization process.
Hence whenever a events stream gets an event, it will write that event to
the file we are defining.
*2. Event publishing from files to analytics server.*
Files will be written with .dat extension.
For example say "api-usage-data.dat".
In APIM v2.2 micro gateway, this file would rotate if the file size exceeds
12mb or after a specific time interval. These values could be set as
configurable values.
Rolled file will be compressed with the timestamp.
eg: *api-usage-data.{timstamp}.zip*
This would reduce 12mb file into (approximately) 4kb file.
Then this zip(s) will be uploaded and persisted in a DB. This will be done
using ballerina tasks(to make it happen periodically).
Then the relevant entries (files) will be read from the DB and populate the
events by reading line by line of that files. Then those events will be
published to the analytics server using existing data publisher.
Thanks,
DinushaD
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439
<https://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] WSO2 API Manager 2.5.0-Alpha Released!
Hi all, Link to wso2-am-2.5.0-Alpha distribution is incorrect in the above mail. Please find the correct distribution links below. Distributions wso2am-2.5.0-Alpha.zip <https://github.com/wso2/product-apim/releases/download/v2.5.0-Alpha/wso2am-2.5.0-Alpha.zip> wso2am-analytics-2.5.0-Alpha.zip <https://github.com/wso2/analytics-apim/releases/download/v2.5.0-Alpha/wso2am-analytics-2.5.0-Alpha.zip> Sorry for the inconvenience caused. Thanks, DinushaD On Sat, Jun 2, 2018 at 3:34 PM, Dinusha Dissanayake wrote: > The WSO2 API Manager team is pleased to announce the release of version > 2.5.0-Alpha of API Manager. > > WSO2 API Manager is a platform for creating, managing, consuming and > monitoring APIs. It employs proven SOA best practices to solve a wide > range of APImanagement challenges such as API provisioning, API gover > nance, API security and API monitoring. It combines some of the most > powerful and mature components of the WSO2's state-of-the-art Carbon > platform to deliver a smooth and end-to-end API management experience > while catering to both API publisher and API consumer requirements. > > WSO2 API Manager is comprised of several modules. > >- API Provider: Define new APIs and manage them >- API Store: Browse published APIs and subscribe to them >- API Gateway: The underlying API runtime based on WSO2 ESB >- API Key Manager: Performs Key Generation and Key Validation >functionalities >- API Traffic Manager: Performs Rate Limiting of API Requests > > For more information on WSO2 API Manager please visit http://wso2.com > /products/api-manager. Also, take a look at the online product > documentation > <https://docs.wso2.com/display/AM2XX/WSO2+API+Manager+Documentation>. > > Distributions > wso2am-2.5.0-Alpha.zip > <https://github.com/wso2/product-apim/archive/v2.5.0-Alpha.zip> > wso2am-analytics-2.5.0-Alpha.zip > <https://github.com/wso2/analytics-apim/releases/download/v2.5.0-Alpha/wso2am-analytics-2.5.0-Alpha.zip> > > How to Run > >1. Extract the downloaded zip >2. Go to the bin directory in the extracted folder >3. Run the wso2server.sh or wso2server.bat as appropriate >4. Launch a web browser and navigate to https://localhost:9443/publ >isher to access the API publisher webapp >5. Navigate to https://localhost:9443/store to access the API store >6. Navigate to https://localhost:9443/admin to access Admin Portal >7. Use "admin", "admin" as the username and password to login as an >admin > > Bug Fixes And Improvements in 2.5.0-Alpha > >- GitHub *(Product-apim ><https://github.com/wso2/product-apim/milestone/46?closed=1>*) >- GitHub (Carbon-apimgt ><https://github.com/wso2/carbon-apimgt/milestone/20?closed=1>) >- GitHub (Analytics-apim ><https://github.com/wso2/analytics-apim/milestone/6?closed=1>) > > Known Issues > > All the open issues pertaining to WSO2 API Manager are reported at the > following location: > >- GitHub (Product-apim ><https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue>), >(Carbon-apimgt > > <https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>), >(Analytics-apim ><https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>) > > How You Can ContributeMailing Lists > > Join our mailing list and correspond with the developers directly. > >- > >Developer List: d...@wso2.org | Subscribe | Mail Archive >- > >User List: u...@wso2.org | Subscribe | Mail Archive > > Reporting Issues > > We encourage you to report issues, documentation faults, and feature > requests regarding WSO2 API Manager through the public API Manager Git > Repo <https://github.com/wso2/product-apim/issues>. > -- The WSO2 API Manager Team -- > > -- > Dinusha Dissanayake > Software Engineer > WSO2 Inc > Mobile: +94712939439 > <https://wso2.com/signature> > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] [Dev] WSO2 API Manager 2.5.0-Alpha Released!
The WSO2 API Manager team is pleased to announce the release of version 2.5.0-Alpha of API Manager. WSO2 API Manager is a platform for creating, managing, consuming and monitoring APIs. It employs proven SOA best practices to solve a wide range of APImanagement challenges such as API provisioning, API governance, API security and API monitoring. It combines some of the most powerful and mature components of the WSO2's state-of-the-art Carbon platform to deliver a smooth and end-to-end API management experience while catering to both API publisher and API consumer requirements. WSO2 API Manager is comprised of several modules. - API Provider: Define new APIs and manage them - API Store: Browse published APIs and subscribe to them - API Gateway: The underlying API runtime based on WSO2 ESB - API Key Manager: Performs Key Generation and Key Validation functionalities - API Traffic Manager: Performs Rate Limiting of API Requests For more information on WSO2 API Manager please visit http://wso2.com /products/api-manager. Also, take a look at the online product documentation <https://docs.wso2.com/display/AM2XX/WSO2+API+Manager+Documentation>. Distributions wso2am-2.5.0-Alpha.zip <https://github.com/wso2/product-apim/archive/v2.5.0-Alpha.zip> wso2am-analytics-2.5.0-Alpha.zip <https://github.com/wso2/analytics-apim/releases/download/v2.5.0-Alpha/wso2am-analytics-2.5.0-Alpha.zip> How to Run 1. Extract the downloaded zip 2. Go to the bin directory in the extracted folder 3. Run the wso2server.sh or wso2server.bat as appropriate 4. Launch a web browser and navigate to https://localhost:9443/publisher to access the API publisher webapp 5. Navigate to https://localhost:9443/store to access the API store 6. Navigate to https://localhost:9443/admin to access Admin Portal 7. Use "admin", "admin" as the username and password to login as an admin Bug Fixes And Improvements in 2.5.0-Alpha - GitHub *(Product-apim <https://github.com/wso2/product-apim/milestone/46?closed=1>*) - GitHub (Carbon-apimgt <https://github.com/wso2/carbon-apimgt/milestone/20?closed=1>) - GitHub (Analytics-apim <https://github.com/wso2/analytics-apim/milestone/6?closed=1>) Known Issues All the open issues pertaining to WSO2 API Manager are reported at the following location: - GitHub (Product-apim <https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue>), ( Carbon-apimgt <https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>), (Analytics-apim <https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>) How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: d...@wso2.org | Subscribe | Mail Archive - User List: u...@wso2.org | Subscribe | Mail Archive Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager through the public API Manager Git Repo <https://github.com/wso2/product-apim/issues>. -- The WSO2 API Manager Team -- -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM][API-Manager gateway] Attaching Labels for APIs
Hi Chamin, On Tue, May 8, 2018 at 11:03 AM, Chamin Dias <cham...@wso2.com> wrote: > Hi all, > > Thanks for the responses. > > This is to communicate a concern/conclusion regarding the flow (attaching > labels). > > *Using the UI (API Publisher)* > > 1. We have decided to fetch the existing labels and provide the option to > select the labels. This improved the user experience because there is no > need to remember the labels in advance. > > 2. In this case, (since the attached labels are already there in the > system) we do not need to validate the labels at API creation time. > Will there be a visibility constraint for the labels? Can all the labels be viewed by anyone? -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM][API-Manager gateway] Attaching Labels for APIs
Hi Dakshika, Tags are for store users searching purpose. So that the subscribers can search APIs based on the tags. Labels are for the gateway level, which is in-fact micro-gateway level. Say you have 100 APIs. But in the micro gateway, you only need to deploy a subset of APIs. We can assign those APIs a particular label (say X). Then for a particular micro gateway we can deploy only the APIs with label X. (Please add if any supporting facts if needed) Thanks, DinushaD. On Tue, May 8, 2018 at 1:19 PM, Dakshika Jayathilaka <daksh...@wso2.com> wrote: > Hi, > > IMO its better if we share the real user story behind the creating labels > in gateway level. (Is it only for grouping purpose? ) > Also whats the difference between current tags vs labels? > > Regards, > > *Dakshika Jayathilaka* > PMC Member & Committer of Apache Stratos > Associate Technical Lead > WSO2, Inc. > lean.enterprise.middleware > 0771100911 > > > On Tue, May 8, 2018 at 11:05 AM Chamin Dias <cham...@wso2.com> wrote: > >> Hi all, >> >> Thanks for the responses. >> >> This is to communicate a concern/conclusion regarding the flow (attaching >> labels). >> >> *Using the UI (API Publisher)* >> >> 1. We have decided to fetch the existing labels and provide the option to >> select the labels. This improved the user experience because there is no >> need to remember the labels in advance. >> >> 2. In this case, (since the attached labels are already there in the >> system) we do not need to validate the labels at API creation time. >> >> >> *Using the REST API* >> >> 1. As discussed, we hope to introduce new section in the payload. >> Eg : >> "labels":[ >> "wso2", >> "development" >> ] >> >> 2. In this approach, the user needs to know the existing labels in >> advance. However, if he types a non existing label (by mistake or >> intentionally), we need to validate the labels at API creation (saving) >> time. We will attach only the existing/valid labels and create the API >> (because adding new labels is an admin task - in admin dashboard). We can >> print a message in the console saying that the invalid labels have been >> skipped. >> >> 3. Accordingly (when using the REST API) we need to do the validation >> call, at API creation time. >> >> Please provide your feedback if you have any optimization for this. >> >> Thanks. >> >> On Mon, May 7, 2018 at 10:33 AM, Sanjeewa Malalgoda <sanje...@wso2.com> >> wrote: >> >>> +1. Lets go with rxt option for the moment as other search options are >>> also based on same design. >>> >>> Thanks, >>> sanjeewa. >>> >>> On Sun, May 6, 2018 at 12:48 AM, Prasanna Dangalla <prasa...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> On Fri, May 4, 2018 at 5:58 PM Nuwan Dias <nuw...@wso2.com> wrote: >>>> >>>>> I think it should be in the rxt as a field. Storing it as a property >>>>> seems like a hack to me. And yes, storing on a separate DB will cause >>>>> complications with queries since the rest of the data is in the rxt. >>>>> >>>> >>>> If we Include as a feild in API rxt, then the search issue that >>>> Malintha pointed out will also be solved. >>>> +1 to go with a feild in the rxt. >>>> >>>> Thanks >>>> Prasanna >>>> >>>>> >>>>> On Fri, May 4, 2018 at 5:45 PM, Malintha Amarasinghe < >>>>> malint...@wso2.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> On Fri, May 4, 2018 at 11:15 AM, Prasanna Dangalla <prasa...@wso2.com >>>>>> > wrote: >>>>>> >>>>>>> >>>>>>> HI, >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, May 4, 2018 at 11:07 AM Chamin Dias <cham...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> On Fri, May 4, 2018 at 9:19 AM, Dinusha Dissanayake < >>>>>>>> dinus...@wso2.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> AFAIU we are going to use labels when downloading a subset of >>>>>>>>>> APIs via Microgateway. If it is not manda
Re: [Architecture] [APIM][API-Manager gateway] Attaching Labels for APIs
> > > > AFAIU we are going to use labels when downloading a subset of APIs via > Microgateway. If it is not mandatory to have the labels, how are we going > to handle the APIs without labels in Microgateway? Are we not going to > download the APIs without labels? > > As Sachini has mentioned above if a subset of APIs to be deployed in the micro gateway, it needs to have a label. Say if APIs have a default label called "def_label". Then if we call "setup def_label", all the APIs will be deployed in the micro gateway. Hence I do not think having a default label would add a significant value. Only the APIs needed to be deployed in the micro gateways will have labels AFAIR. (please correct me if I am wrong) Thanks, DinushaD. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM] Label feature for API-Manager gateway
>> Are we adding a default label for APIs when creating/publishing? >> > > Do we have a need to? > If the label is not mandatory , I think we would not need a default label. Thanks, DinushaD -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM] Label feature for API-Manager gateway
Hi Krishan, What is the difference between UUID and Label_ID? Thanks, DinushaD. On Wed, May 2, 2018 at 6:26 PM, Krishan Wijesena <krish...@wso2.com> wrote: > Hi All, > > > Currently, I'm working on the Labeling feature for API Manager gateway. > API Manager need to allows adding labels to the APIs in create/update > phases from the publisher, so that labels help to grouping APIs into API > manager gateway. > > If the user requests the particular label, then it provides the set of > APIs that deploy in the same gateway. > > As initial phase, labels should be defined by the admin(Super/Tenant) > using admin dashboard and the particular label should have set of > properties. > > To do that I need to introduce AM_LABEL table to the AM database to store > the labels and it’s schema as follows. > > LABEL_ID is the primary key and (NAME & TENANT_ID) is Unique. > > Label should have separate Http and Https basepath. > > > > > *Multi-Tenant support* > > We need to support the multi-tenancy of the adding labels. > > Super/Tenant admin can define new labels based on the requirement. > > So I introduce the TENANT_ID field to the AM_LABEL table. > > For example, Tenant_admin_A and Tenant_admin_B can introduce the same > label "X" which have two base_path. > > Comments or suggestions are highly appreciated. > > Thanks & Regards > -- > > *Krishan Wijesena* > Software Engineer | WSO2 > > Email : krish...@wso2.com > Mobile : +94776219923 > WSO2 Inc : http://wso2.com > [image: http://wso2.com/signature] <http://wso2.com/signature> > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM] CLI support for Importing and Exporting Applications
-+--+ >> * >> >> >> On Thu, Jan 25, 2018 at 5:41 PM, Randilu Soysa <rand...@wso2.com> wrote: >> >>> Hi everyone, >>> >>> I’m working on a project to introduce commands to provide application >>> import export support for the import-export-cli for APIM 2.x. I am planning >>> to introduce commands in order to list available applications of a specific >>> user, export an application from a desired environment and import an >>> application to a desired environment. >>> >>> >>> The commands are as follows, >>> >>> >>> Exports an Application from a desired environment >>> >>> Commands >>> >>> export-app >>> >>> Flags >>> Required >>> -n, --name string Name of the Application to be exported >>> -i, --uuid string UUID of the Application to be exported >>> -e, --environment string Environment from which the Application >>> should be exported >>> Optional >>> -p, --password string Password >>> -u, --username string Username >>> >>> -k, --insecure Allow connections to SSL endpoints >>> without certs >>> --verbose Enable verbose mode >>> >>> apimcli export-app (--name --uuid >>> --environment >>> ) [flags] >>> >>> Examples: >>> >>> apimcli export-app -n SampleApp >>> 9f6affe2-4c97-4817-bded-717f8b01eee8 -e dev >>> apimcli export-app -n SampleApp >>> 7bc2b94e-c6d2-4d4f-beb1-cdccb08cd87f -e prod >>> >>> >>> >>> <https://github.com/randilu/WatchOver/new/master?readme=1#imports-an-application-to-a-desired-environment>Imports >>> an Application to a desired environment >>> >>> Commands >>> >>> import-app >>> >>> Flags >>> Required >>> -f, --file string Name of the Application to be imported >>> -e, --environment string Environment from the which the >>> Application should be imported >>> Optional >>> -s, --addSubscriptions Adds subscriptions of the Application >>> -o, --perserveOwnerPreserves app owner from the original >>> Environment >>> -p, --password string Password >>> -u, --username string Username >>> >>> -k, --insecure Allow connections to SSL endpoints >>> without certs >>> --verbose Enable verbose mode >>> >>> apimcli import-app (--file --environment >>> ) [flags] >>> >>> Examples: >>> >>> apimcli import-app -f qa/sampleApp.zip -e dev >>> apimcli import-app -f staging/sampleApp.zip -e prod -u admin -p >>> admin >>> apimcli import-app -f qa/sampleApp.zip --preserveOwner >>> --addSubscriptions -e prod >>> >>> >>> >>> <https://github.com/randilu/WatchOver/new/master?readme=1#lists-the-applications-available-for-a-certain-user>Lists >>> the Applications available for a certain user >>> >>> Commands >>> >>> list apps >>> >>> Flags >>> Required >>> -e, --environment >>> Optional >>> -u, --username >>> -p, --password >>> >>> >>> Examples: >>> >>> apimcli list apps -e dev >>> apimcli list apps -e staging >>> apimcli list apps -e staging -u admin -p 123456 >>> apimcli list apps -e staging -u admin >>> apimcli list apps -e staging -p 123456 >>> >>> >>> Your suggestions and feedback on this is highly appreciated! >>> >>> >>> -- >>> *Randilu Soysa* >>> Software Engineering Intern | WSO2 >>> >>> Email: rand...@wso2.com >>> Mobile : +94 77 197 5078 <+94%2077%20197%205078> >>> linkedin : linkedin.com/in/randilusoysa >>> Web : http://wso2.com >>> >>> <http://wso2.com/signature> >>> >> >> >> >> -- >> *Randilu Soysa* >> Software Engineering Intern | WSO2 >> >> Email: rand...@wso2.com >> Mobile : +94 77 197 5078 >> linkedin : linkedin.com/in/randilusoysa >> Web : http://wso2.com >> >> <http://wso2.com/signature> >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Naduni Pamudika* > Software Engineer | WSO2 > Mobile: +94 719 143658 <+94%2071%20914%203658> > [image: http://wso2.com/signature] <http://wso2.com/signature> > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [RRT] XACML based scope validator (during OAuth2 token validation)
gt;>>>>>>>> overhead in configuring and doesn't work well with >>>>>>>>>>>>>>>>>>>>>> tenant model. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> The current scope-role based validation we introduced >>>>>>>>>>>>>>>>>>>>>> in IS 5.4.0 will need to be implemented using XACML and >>>>>>>>>>>>>>>>>>>>>> be the default >>>>>>>>>>>>>>>>>>>>>> policy. The other policies you were planning could be >>>>>>>>>>>>>>>>>>>>>> additional template >>>>>>>>>>>>>>>>>>>>>> policies we ship with the product. In addition users can >>>>>>>>>>>>>>>>>>>>>> have any new >>>>>>>>>>>>>>>>>>>>>> policies they want (per tenant). >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Because I have checked with >>>>>>>>>>>>>>>>>>>>>>> identity-application-authz-xacml[1 >>>>>>>>>>>>>>>>>>>>>>> <https://github.com/wso2-extensions/identity-application-authz-xacml>] >>>>>>>>>>>>>>>>>>>>>>> and planned to implement validating scopes against the >>>>>>>>>>>>>>>>>>>>>>> role base and time >>>>>>>>>>>>>>>>>>>>>>> base policies only. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Yes, you can use this code and implement a XACML PEP >>>>>>>>>>>>>>>>>>>>>> to send a XACML request. But the validation has to >>>>>>>>>>>>>>>>>>>>>> happen on the XACML PDP >>>>>>>>>>>>>>>>>>>>>> side. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> What is the difference between the role based policy >>>>>>>>>>>>>>>>>>>>>> you are talking and the role based scope validation we >>>>>>>>>>>>>>>>>>>>>> implemented in IS >>>>>>>>>>>>>>>>>>>>>> 5.4.0? >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> XACML based scope validation would give fine-grained >>>>>>>>>>>>>>>>>>>>> control and flexilibility. I don't have experience with >>>>>>>>>>>>>>>>>>>>> JDBC scope >>>>>>>>>>>>>>>>>>>>> validator but from what I know, it is hard to have a >>>>>>>>>>>>>>>>>>>>> generic implementation >>>>>>>>>>>>>>>>>>>>> out of it. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> The added avantage is flexibility. You can write your >>>>>>>>>>>>>>>>>>>>> custom XACML policies and control how authorization >>>>>>>>>
Re: [Architecture] [APIM] [C4] Custom header field for OAuth2 token per tenant
exists in the api-manager.xml then the existing >>> workflow will execute using the "Authorization" header field. >>> >>> >>> ii) Proposed workflow for restricting the access token from being passed >>> to the backend. >>> >>> a) Read the "RemoveOAuthHeadersFromOutMessage" config from the >>> "tenant-conf.json" >>> >>> b) If no config exists in tenant-conf.json, then read it from the >>> "api-manager.xml" >>> >>> >>> Any ideas and suggestions are highly appreciated! >>> >>> Thanks, >>> Viduranga. >>> >>> [1] https://docs.wso2.com/display/AM210/Working+with+Access+Tokens >>> -- >>> Regards, >>> >>> *Viduranga Gunarathne* >>> >>> *Software Engineer Intern* >>> >>> >>> *WSO2* >>> Email : vidura...@wso2.com >>> Mobile : +94712437484 <+94%2071%20243%207484> >>> Web : http://wso2.com >>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>> >> >> >> >> -- >> Nuwan Dias >> >> Software Architect - WSO2, Inc. http://wso2.com >> email : nuw...@wso2.com >> Phone : +94 777 775 729 <+94%2077%20777%205729> >> > > > > -- > Regards, > > *Viduranga Gunarathne* > > *Software Engineer Intern* > > > *WSO2* > Email : vidura...@wso2.com > Mobile : +94712437484 <+94%2071%20243%207484> > Web : http://wso2.com > [image: https://wso2.com/signature] <https://wso2.com/signature> > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <+94%2071%20293%209439> <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM][C5] Siddhi Apps( forThrottle Policies) Deployment with CEP
+Adding architecture On Thu, Jun 29, 2017 at 5:05 PM, Nuwan Dias <nuw...@wso2.com> wrote: > Let's discuss publicly please, this thread is internal only. > > On Thu, Jun 29, 2017 at 5:01 PM, Dinusha Dissanayake <dinus...@wso2.com> > wrote: > >> Hi All, >> >> In earlier versions of APIM, throttle policy deployment for CEP was >> handled using push mechanism meaning APIM itself had to deploy throttle >> policies in CEP. If there are multiple CEP nodes, then the Siddhi >> apps/execution plans syncing would be an issue here. >> >> We were thinking of pull based mechanism from CEP side to overcome this. >> To do that, from APIM side we need to add an API to the core which allows >> CEP to get all Siddhi apps for existing throttle policies. Then every CEP >> node will call APIM (once or periodically) and then it will check the DB >> and generate a zip containing all the Siddhi Apps for existing throttle >> policies. >> >> >> This API will only need GET resource. The resource path for this API >> would be *"export/policies/throttle"*. As mentioned above, this will >> return a zip. Mutual SSL would be used to secure the API since if we use >> OAuth2, then the token may expire in a while. >> >> Exported zip can be manually deployed in the CEP or deployment can be >> done using e a curl command. If this needs to be happened periodically, >> then a cron job can be written. >> >> Please provide suggestions for improvements. >> >> Thanks & Regards. >> -- >> Dinusha Dissanayake >> Software Engineer >> WSO2 Inc >> Mobile: +94712939439 <+94%2071%20293%209439> >> <https://wso2.com/signature> >> > > > > -- > Nuwan Dias > > Software Architect - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 <+94%2077%20777%205729> > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <+94%2071%20293%209439> <https://wso2.com/signature> ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
