Re: [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC4
Hi, Tested the following in API Manager RC4. No issues found. 1. Basic API and Application flow - API Creation, Publishing, Key generation, Subscription and Invocation. 2. Creating New API Version 3. Deploy and invoke Prototyped APIs 4. Customizing API LifeCycle 5. API Documentation 6. Publishing to multiple External API Stores 7. Create and Publish SOAP APIs [+] - Stable - go ahead and release Thanks, Tharika. On Fri, Jun 22, 2018 at 12:24 PM Chamalee De Silva wrote: > Hi, > I tested following in API Manager RC4. > > 1. Basic API flow > - API creation, publishing, invocation etc. > 2. Creating users and roles, and user permissions. > 3. API documentation > 4. Forums in API Store > > 5. Single Sign On with WSO2 Idnetity Server (WSO2 IS 5.6.0 RC3) > - SP init and IDP init SSO > - Assertion Encryption > - Single logout on/off > - SAML request singning in store and publisher. > > 6. Installing SCIM identity feature in API Manager 2.5.0 > 7. API Properties > 8. SDK generation feature > > > [+] - Stable - go ahead and release > > > Thanks, > Chamalee > > > On Fri, Jun 22, 2018 at 12:16 PM, Chamin Dias wrote: > >> Hi, >> >> Tested following (for both super tenat and tenat) and no issues found. >> >> a) Label creation/update >> b) Attaching/removing labels to/from APIs >> c) Displaying label information in Publisher and Store >> >> [+] Stable - go ahead and release >> >> Thanks. >> >> On Fri, Jun 22, 2018 at 12:15 PM, Krishan Wijesena >> wrote: >> >>> Hi, >>> I have tested following and no issues found. >>> >>> 1. Basic API flow >>> - API creation, publishing, invocation. >>> 2. Admin REST API >>> 3. Adding new Throttling policies >>> - Advanced policies >>> - Subscription policies >>> - Application policies >>> - Block list policies >>> 4. Microgateway label add/update REST API >>> 5. Test with browser IE 11 >>> - basic flow (Super tenant/tenant) >>> - Label add/update >>> >>> [+]Stable - go ahead and release >>> >>> Thanks, >>> krishan. >>> >>> >>> >>> On Thu, Jun 21, 2018 at 10:36 PM, Chamin Dias wrote: >>> >>>> Hi all, >>>> >>>> We are pleased to announce the fourth release candidate of WSO2 API >>>> Manager 2.5.0. >>>> >>>> This release fixes the following issues. >>>> Fixes : carbon-apimgt >>>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93&q=is%3Aclosed+closed%3A2018-03-16..2018-06-21+-label%3A%22APIM+3.0.0%22> >>>> Fixes : product-apim >>>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93&q=is%3Aclosed+closed%3A2018-03-16..2018-06-21+-label%3A3.0.0> >>>> Fixes : analytics-apim >>>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93&q=closed%3A2018-03-16..2018-06-21+is%3Aclosed> >>>> >>>> Source and distribution, >>>> Runtime : >>>> https://github.com/wso2/product-apim/releases/tag/v2.5.0-rc4 >>>> Analytics : >>>> https://github.com/wso2/analytics-apim/releases/tag/v2.5.0-rc1 >>>> >>>> Please download, test the product and vote. >>>> >>>> [+] Stable - go ahead and release >>>> [-] Broken - do not release (explain why) >>>> >>>> *Note : We can still use APIM-Analytics 2.5.0-rc1 for analytics (no >>>> issues reported so far).* >>>> >>>> Thanks, >>>> WSO2 API Manager Team. >>>> >>>> -- >>>> Chamin Dias >>>> Mobile : 0716097455 >>>> Email : cham...@wso2.com >>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@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 >> Dev@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 > Dev@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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] userinfo not received
Hi Shib, Only the username (sub) information will be available in the response when calling the */userinfo* endpoint by default. You can customize the information to be returned in the response by configuring claims of the relevant Service Provider generated for the Application created in API Store. You can refer [1] in order to achieve this. [1] https://docs.wso2.com/display/IS530/Configuring+Claims+for+a+Service+Provider Thanks, Tharika. On Tue, Jun 12, 2018 at 4:39 PM shibsankar wrote: > I have LDAP User store configured in WSO2. > > I am calling *userinfo *API to get user info for a given user *access > token. * > > ( This *access token* has been generated for a given LDAP username & > password with grant type is password ) > > I was expecting *userinfo API* to respond with user First Name & Last > Name but it did not. > > Please see the screenshot attached. > > How to fix this? > > > > Regards > Shib > > ___ > Dev mailing list > Dev@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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Custom authentication error message in APIM
Hi Vivek, You could try this [1] out to customize your error message. Alter the sample based on your requirement. [1] http://sanjeewamalalgoda.blogspot.com/2015/06/how-to-send-specific-status-code-and.html Thanks, Tharika. On Mon, Oct 2, 2017 at 6:46 PM, vivekkumar wrote: > Any clue from anybody ? > > > > -- > Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2- > Development-f3.html > ___ > Dev mailing list > Dev@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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Yasima Dewmini
Congratulations Yasima..!! Wish you all the best. On Mon, Jul 3, 2017 at 8:52 AM, Naduni Pamudika wrote: > Congratulations Yasima !!! > > On Fri, Jun 30, 2017 at 9:22 PM, Chamalee De Silva > wrote: > >> Congratulations Yasima >> >> >> >> >> On Fri, Jun 30, 2017 at 3:03 PM, Harsha Kumara wrote: >> >>> Congratulations! >>> >>> On Fri, Jun 30, 2017 at 1:41 PM, Tharindu Dharmarathna < >>> tharin...@wso2.com> wrote: >>> >>>> Congratulations Yasima! >>>> >>>> >>>> On Fri, Jun 30, 2017 at 1:31 PM, Roshan Wijesena >>>> wrote: >>>> >>>>> Congratulations Yasima! >>>>> >>>>> On Fri, Jun 30, 2017 at 1:20 PM, Sanjeewa Malalgoda >>>> > wrote: >>>>> >>>>>> Hi All, >>>>>> It's my pleasure to welcome Yasima Dewmini as a WSO2 Committer. >>>>>> >>>>>> Yasima has been a valuable contributor to the WSO2 API Manager >>>>>> team. In recognition of her contribution, dedication, and commitment she >>>>>> has been voted as a WSO2 committer. >>>>>> >>>>>> Yasima, Congratulations and keep up the good work! >>>>>> >>>>>> Thank You, >>>>>> sanjeewa. >>>>>> -- >>>>>> >>>>>> *Sanjeewa Malalgoda* >>>>>> WSO2 Inc. >>>>>> Mobile : +94713068779 <+94%2071%20306%208779> >>>>>> >>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>>>> :http://sanjeewamalalgoda.blogspot.com/ >>>>>> <http://sanjeewamalalgoda.blogspot.com/> >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Roshan Wijesena. >>>>> Senior Software Engineer-WSO2 Inc. >>>>> Mobile: *+94719154640 <+94%2071%20915%204640>* >>>>> Email: ros...@wso2.com >>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>>>> lean.enterprise.middleware. >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Tharindu Dharmarathna*Senior Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> mobile: *+94779109091 <+94%2077%20910%209091>* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Harsha Kumara >>> Software Engineer, WSO2 Inc. >>> Mobile: +94775505618 <+94%2077%20550%205618> >>> Blog:harshcreationz.blogspot.com >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks & Regards, >> >> *Chamalee De Silva* >> 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 >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Naduni Pamudika* > Software Engineer | WSO2 > Mobile: +94 719 143658 <+94%2071%20914%203658> > [image: http://wso2.com/signature] <http://wso2.com/signature> > > ___ > Dev mailing list > Dev@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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] SCIM filtering when same user or role exists in multiple user stores
Hi Tharindu, Got it. Thanks for the reply. Thanks, Tharika On Mon, Jun 26, 2017 at 12:12 PM, Tharindu Dharmarathna wrote: > Hi Tharika, > > As I tested in IS 5.3.0 if we do *Eq* operation it will only retrieve > according to the specific user store given in user search. > > *GET /Users?filter=userNameEqJohn ==> return user in primay * > *GET /Users?filter=userNameEqWSO2/John ==> return user in secondry user > store WSO2 * > > Thanks > > On Mon, Jun 26, 2017 at 12:06 PM, Tharika Madurapperuma > wrote: > >> Hi All, >> >> How does the SCIM endpoint in IS behave during GET requests when the same >> user or role exists in multiple user stores? >> >> For example, if there is a user called John in both the Primary user >> store and the Secondary user store, when we perform a search for the user >> John by doing a GET request on >> >> *GET /Users?filter=userNameEqJohn,* >> >> assuming both Primary and Secondary user stores are enabled, will it >> return both the users? >> >> Thanks, >> Tharika. >> >> -- >> *Tharika Madurapperuma* >> Software Engineer | WSO2, Inc. >> >> Email : thar...@wso2.com >> Mobile : +94777875624 <+94%2077%20787%205624> >> Web : http://wso2.com >> >> <http://wso2.com/signature> >> > > > > -- > > *Tharindu Dharmarathna*Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: *+94779109091 <+94%2077%20910%209091>* > -- *Tharika Madurapperuma* Software Engineer | WSO2, Inc. Email : thar...@wso2.com Mobile : +94777875624 Web : http://wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] SCIM filtering when same user or role exists in multiple user stores
Hi All, How does the SCIM endpoint in IS behave during GET requests when the same user or role exists in multiple user stores? For example, if there is a user called John in both the Primary user store and the Secondary user store, when we perform a search for the user John by doing a GET request on *GET /Users?filter=userNameEqJohn,* assuming both Primary and Secondary user stores are enabled, will it return both the users? Thanks, Tharika. -- *Tharika Madurapperuma* Software Engineer | WSO2, Inc. Email : thar...@wso2.com Mobile : +94777875624 Web : http://wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] Bulk retrieval of SCIM Groups given multiple group IDs
Hi All, With the implementation of the API Permissions model in APIM 3.0, we need to get the groupIds for a set of groups/roles. Instead of making multiple calls to the SCIM endpoint for retrieving each group, doing it in a single call to the API would be more effective in terms of performance. Does SCIM API in IS support bulk retrieval of SCIM Groups given a list of group IDs? Thanks, Tharika. -- *Tharika Madurapperuma* Software Engineer | WSO2, Inc. Email : thar...@wso2.com Mobile : +94777875624 <+94%2077%20787%205624> Web : http://wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture][IS][APIM] Providing a SCIM Id for admin user in SCIM
Hi All, In APIM 3.0, we plan to have a feature for enabling Read, Update, Delete permissions for an API based on roles in API Publisher. For user validation purposes, we need to retrieve the list of roles for the loggedin user. This role list is retrieved using the user's SCIM Id. But since the admin user by default does not have an ID as per [1] and is not regarded as a SCIM user, we wont be able to retrieve the list of roles for the admin. There are two possible options for making this work. *Option 1: *Either from APIM 3.0 side we should make a call to the SCIM endpoint and update the admin user to have a SCIM ID as in [1], preferably during startup or * Option 2: *We can make the admin user have an Id by default from SCIM Implementation in IS. If we go with Option 1, it amounts to an additional call to the SCIM endpoint to update the user and a question arises as to where we should be updating it. The SCIM Id for the admin user is needed only in this scenario for retrieving roles currently, hence updating the admin user during startup is questionable. IMO Option 2 is preferrable because it will not result in an additional update as in Option 1 above. WDYT? Will there be any plans to include this capability in IS 5.4.0? [1] [Dev] [IS] Admin/Tenant Admin Users cannot be filtered to get the SCIM ID Thanks, Tharika. -- *Tharika Madurapperuma* Software Engineer | WSO2, Inc. Email : thar...@wso2.com Mobile : +94777875624 Web : http://wso2.com <http://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Is there a hard and fast rule to chose java 8 streams over for loops
Hi Rajith, IMO Java streams should not be used always as a practice. It is not a silver bullet. There can be issues in performance in some cases as you have pointed out. One of the main advantage of using streams is when the logic of looping is quite complex and involves different operations on collections together, so that it can improve readability and understandability. But at the same time it can result in new and subtle bugs if we are not careful enough [1]. The performance aspect of streams vs loops depends on the type of the collection and the situation they deal with. This performance difference can sometimes be negligible. Hence we cannot completely go with one against another. So IMHO we can consider using streams only when necessary based on our requirement and use loops where it deserves. [1] https://blog.jooq.org/2014/06/13/java-8-friday-10-subtle-mistakes-when-using-the-streams-api/ Thanks, Tharika. On Thu, Mar 30, 2017 at 12:01 PM, Rajith Roshan wrote: > Hi all, > > Most of our C5 development have used java8 streams api frequently more > than the for loops. > But there are some research have done to compare the performance of > streams api compared to for loops. They have shown that stream API is slow > compared to for loops in many scenarios (even for parallel streams). [1][2] > > Is there any proper guidance to use which one over the other or are we > using streams as a practice in C5 development > > [1] - https://blog.jooq.org/2015/12/08/3-reasons-why-you- > shouldnt-replace-your-for-loops-by-stream-foreach/ > [2] - https://jaxenter.com/java-performance-tutorial-how-fast- > are-the-java-8-streams-118830.html > > Thanks! > Rajith > > -- > Rajith Roshan > Software Engineer, WSO2 Inc. > Mobile: +94-72-642-8350 <%2B94-71-554-8430> > > ___ > Dev mailing list > Dev@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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Find bugs security issue with Md5 hashing
Hi Nuwan,
The hashing algorithm is determined from the handshake. The
WWW-Authenticate response header will optionally contain an algorithm
directive.
In the DigestAuthMediator, if we receive any other algorithm
apart from MD5 or MD5-sess, we consider it as MD5 and carry out the
hashing. Finally, when the hash is calculated, we send the algorithm used
by our side, in the Authorization header of the request directed back to
the endpoint. So then that endpoint knows which algorithm we used.
So in the current implementation, only MD5 and MD5-sess
algorithms are supported as per the RFC [1].
[1] https://tools.ietf.org/html/rfc2617
Tharika Madurapperuma
Intern - Software Engineering
WSO2, Inc.
Mobile : +94777-875-624
On Wed, Jan 13, 2016 at 3:38 PM, Nuwan Dias wrote:
> @Tharika, how is the hashing algorithm determined? Is it determined
> through the handshake between the gateway and the back-end or is it
> hard-coded?
>
> AFAIU the hashing algorithm should be determined at the handshake so that
> the client (Gateway) and back-end use the same hashing mechanism to hash
> the strings for comparison.
>
> On Wed, Jan 13, 2016 at 2:23 PM, Shani Ranasinghe wrote:
>
>> + Dev
>>
>> On Wed, Jan 13, 2016 at 2:18 PM, Shani Ranasinghe wrote:
>>
>>> Hi,
>>>
>>> In the gateway package we have a class "DigestAuthMediator" which uses
>>> Md5 hashing, to compute the hashes for digest authentication. Findbugs
>>> complains that the message digest is weak[1]. It recommends that we use
>>> one of the following algorithms SHA-1, SHA-224*, SHA-256, SHA-384, SHA-512,
>>> SHA-512/224, or SHA-512/256.. I spoke to a member of the security team and
>>> they too recommended the same (use hashing method like SHA 256). However,
>>> we have implemented the hashing in this class based on a spec [2] which
>>> indicates that by default it uses the MD5 algorithm, else wise the server
>>> could specify the algorithm ("MD5" | "MD5-sess" | token).
>>>
>>> How do we handle this scenario?
>>>
>>>
>>> [1] MessageDigest Is Weak
>>> The algorithm used is not a recommended MessageDigest.
>>> NIST recommends the use of SHA-1, SHA-224*, SHA-256, SHA-384, SHA-512,
>>> SHA-512/224, or SHA-512/256.
>>> * SHA-224 algorithm is not provided by SUN provider.
>>> Upgrade your implementation to use one of the approved algorithms. Use
>>> an algorithm that is sufficiently strong for your specific security needs.
>>>
>>> [2] https://tools.ietf.org/html/rfc2617
>>>
>>> --
>>> Thanks and Regards
>>> *,Shani Ranasinghe*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 77 2273555
>>> Blog: http://waysandmeans.blogspot.com/
>>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>>>
>>
>>
>>
>> --
>> Thanks and Regards
>> *,Shani Ranasinghe*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273555
>> Blog: http://waysandmeans.blogspot.com/
>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>>
>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Request time out when sending a PATCH request in tenant mode
Hi Chanaka, I created a public jira ticket for this issue. Thanks in advance. Thanks, Tharika. Tharika Madurapperuma Software Engineering Intern WSO2 Mobile : +94777-875-624 On Tue, Nov 17, 2015 at 9:58 AM, Chanaka Fernando wrote: > Hi Tharika, > > Please create a public jira ticket for this issue if there is no such > issue reported already and make the priority as high. ESB team will look > into this issue with a future ESB release. > > Thanks, > Chanaka > > On Tue, Nov 17, 2015 at 9:45 AM, Tharika Madurapperuma > wrote: > >> >> Hi, >> >> When sending a PATCH request from an API using the latest ESB pack >> (Version 4.9.0), as a tenant user, the request gets timed out and there is >> no response from the server. However this works fine with the super tenant. >> >> I tested this in API-Manager which uses the synapse version 2.1.4-wso2v1. >> The same issue persists. >> >> Appreciate if this can be fixed soon. >> >> Thanks, >> Tharika. >> >> Tharika Madurapperuma >> Software Engineering Intern >> WSO2 >> Mobile : +94777-875-624 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thank you and Best Regards, > Chanaka Fernando > Senior Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > > > > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Request time out when sending a PATCH request in tenant mode
Hi, When sending a PATCH request from an API using the latest ESB pack (Version 4.9.0), as a tenant user, the request gets timed out and there is no response from the server. However this works fine with the super tenant. I tested this in API-Manager which uses the synapse version 2.1.4-wso2v1. The same issue persists. Appreciate if this can be fixed soon. Thanks, Tharika. Tharika Madurapperuma Software Engineering Intern WSO2 Mobile : +94777-875-624 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
