Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

Tested the following. Store REST API External Stores Store tag listing and tagwiseMode [+] Stable - go ahead and release Thanks & Regards, Ishara Cooray Senior Software Engineer Mobile : +9477 262 9512 WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware > >

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

Hi all, I tested the following samples in the editor. - AggregateDataIncrementally - AggregateOverTime - RDBMSSample - StreamingRegressor - SweetProductionDataPreprocessing - JoinWithStoredData [+] Stable go ahead and release Best regards, Chathuranga Siriwardhana, Software

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

Hi All, I've smoke tested following on Windows 10 Chrome. - Editor - Business Rules - Status Dashboard - Dashboard Portal No issues found. [+] Stable - go ahead and release. Best regards Eranga. On Mon, Sep 17, 2018 at 10:29 AM Anusha Jayasundara wrote: > Hi All, > > I have

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

Hi All, I have tested followings, 1. Minimum HA scenario - Setup 2 nodes - Change Passive to active - Data persistence between two nodes - Monitoring dashboard for the HA scenario 2. Editor Samples - Redis Sample - IBMMQSample - RDBMS Sample

Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.7.0 RC3

Hi All, Thanks for testing WSO2 Identity Server 5.7.0-RC3. Since this vote passed with 28 +1s and 0 -1s, we’re hereby closing this vote and proceeding with the Identity Server 5.7.0 GA release. Thanks, Thanuja On Mon, Sep 17, 2018 at 10:01 AM Dilin Dampahalage wrote: > Hi all, > > I have

Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.7.0 RC3

Hi all, I have tested IS 5.7.0-RC3 with IS Analytics 5.7.0 Beta and it works fine. No issues were found. [+] Stable - go ahead and release Thanks, Dilin On Sun, Sep 16, 2018 at 9:09 AM Abilashini Thiyagarajah wrote: > Hi all, > > I have tested the following scenarios, > > - Role-based

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

Hi All, I have tested following. 1. Basic dashboard functionalities - Create dashboard - Drag and drop widgets - Create Pages in dashboard - Hide Pages 2. Dashboard import / export feature 3. Dashboard and widget report generation feature No issues found. [+]

Re: [Architecture] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

Tested the following. Siddhi Stores Query API[editor/worker runtime] Distributed Message Tracer[worker/dashboard runtime] SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver) runtimes] Editor Sample: - Store RDBMS MySQL/Oracle[editor] - Store Cassedra[editor] No blockers

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

Thank you Le dim. 16 sept. 2018 à 19:54, Fazlan Nazeem a écrit : > Hi Nicolas, > > Yes. Usually, the use case you described is achieved via a JWT token which > has data related to the user who invoked the API in API Manager. This > will not include the user password, but the username will be

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

Hi Nicolas, Yes. Usually, the use case you described is achieved via a JWT token which has data related to the user who invoked the API in API Manager. This will not include the user password, but the username will be included. On the backend web service, you can decode the JWT and do any

Re: [Architecture] [APIM][300][Store] Feature to change password of an user

On Thu, Sep 6, 2018 at 5:31 PM Vithursa Mahendrarajah wrote: > Hi Dulanja, > > Please find my answers in-line: > > On Thu, Sep 6, 2018 at 10:45 AM Dulanja Liyanage wrote: > >> Hi Vithursa, >> >> Few questions: >> >> 1. What happens when the user enters a wrong username? As a security best >>

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

hi Fazlan, Sure, when we use service on WSO2 API-M, we use WSO2-IS to manage token. We would like to secure webservice and make sure only people allowed to see the informations can do it, so we would like to provide when making a query, the credentials of the person associated to the token, so

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

Hi Nicolas, Your question is not very clear to me. Can you explain a bit in detail? On Sun, Sep 16, 2018 at 11:19 AM Nicolas Maujean < nicolas.maujean.fra...@gmail.com> wrote: > hi Fazlan, > >Thank you for your feedback. Yes, WSO2 API-Manager, can we add the > credentials associated to the

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

hi Fazlan, Thank you for your feedback. Yes, WSO2 API-Manager, can we add the credentials associated to the token in oauth2 ? best regards, Nicolas Maujean Le dim. 16 sept. 2018 à 18:32, Fazlan Nazeem a écrit : > Hi Nicolas, > > I assume your question is regarding API Manager product. You

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

Hi, I have tested the below scenarios. - Adding a secondary userstore - Adding a user to the secondary userstore - Adding a role to the secondary userstore Using the *secondary user* created tested the following operations - Basic API Creation in Publisher - Application

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

Hi Nicolas, I assume your question is regarding API Manager product. You can append query params to the backend URL by adding a mediation flow to the API in the inSequence. http://ws.apache.org/ns/synapse; name="sample"> > expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'), >

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

Hi All, Tested following scenarios. - Workflows - Super-tenant/Tenant flow API Subscription Workflow Application Creation Workflow Configure Workflow for tenants - Subscription blocking/ unblocking - Tested With IE 11 browser. Basic API

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

Hi all, Tested below. 1. Basic user creation API creation, subscription and invocation. 2. Microgateway with API labels 3. Throttling (subscription, application and advanced) 4. APIM gateway and microgateway with analytics. No blockers found. [+] Stable - Go ahead and release Thanks, DinushaD

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

Hi all, I have tested following and no issues found: - Basic API flow - API creation, publishing and invocation - Create user with different roles - API documentation - Password recovery in API Store - User sign-up workflow - Add application with custom attributes - Block

[Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

Hi, Is it possible to add information automatically in the url calling the back end, givng enough information, the credentials allowing to the backend to make further test for security purpose ? best regards, Nicolas Maujean ___ Architecture

Re: [Architecture] API-M and sticky session

Hi Tharindu, Thank you for your feedback. Some More questions : - Why don’t use the sticky module of nginx which is free but nginx plus ? - why validate tokens ? With share folder, tokens is not shared ? - I don’t understand for UI components, can you provide me an example ? Best regards,

Re: [Architecture] API-M and sticky session

Hi Nicolas, The sticky session in API MAnager is needed to manage the following aspects. 1. In all UI components, it needs to manage to keep session affinity for keep session with the same instance 2. For all Admin Service Calls which use to validate tokens, Create APIS, etc between nodes. it

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

Hi All, tested the following in distributed setup - Advance Throttling Policies - Blocking Conditions - Custom Rules [+] Stable - go ahead and release On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika wrote: > Hi All, > > Tested the following with PostgreSql 9.5. > > - Basic API creation and