Amalka Subasinghe's Blog

When using nginx in front of several applications, In coming requests come to the nginx as encoded parameters but it reached to the backend application as decoded parameters. Because of that backend application rejects the massage since it accept encoded parameter. In order to solve this problem, with the following configuration we can stop decoding query parameters at the nginx level. location /t/ {                 proxy_set_header X-Real-IP $remote_addr;                  ------                  ------ #               proxy_next_upstream error timeout invalid_header http_500;                  proxy_pass https://amalkaorg.app1.wso2apps.com$ request_uri ;         } The parameter added as $request uri is the full original request URI (with arguments)

1. Login to Admin Dashboard from the admin user. ( https://api.cloud.wso2.com/ad min/ ) 2. Click Black List under the Throttle Policies section and click Add Item (Refer to the screenshot below) 3.  Select the condition type as the user and give the full qualified username as the value and click blacklist. (Refer to the screenshot below) For example, if you want to block the user amalka@wso2.com  from invoking APIs, you have to provide the value as amalka@wso2.com@amalkaorg  by appending the organization key at the end of the username with '@' character.  If you follow the above steps, the user will not be able to invoke APIs. Also please note that if you blacklist, the user will not be able to invoke any API until you remove the blacklist policy.

In WSO2 Integration Cloud, we provide WSO2 ESB as an app type. So you can configure to FHIR connector on WSO2 ESB.   At the moment we don't have a specific document on configuring the FHIR connector on WSO2 Integration Cloud. But, we have included an example document [1] on how to configure a sample (Twitter) connector. This is a general guide a user can follow, it shows how to create a CAR file and import it onto the Integration Cloud. For information on configuring the FHIR connector, you can follow the document here.[2] Please note that if you wants to add custom server certificates into the client truststore or requires any custom configurations, you need to create custom docker image and deploy it in WSO2 Integration Cloud. [3] [1]. https://docs.wso2.com/display/ IntegrationCloud/Use+a+WSO2+ ESB+Connector+to+Invoke+Third+ Party+Functionality [2]. https://docs.wso2.com/display/ ESBCONNECTORS/FHIR+REST+ Connector [3]. https://docs.wso2.com/display/ In

Let's say I have published a API and I want to let my API store users how they can use the API. Currently this can be done by adding API documentation. So with this you will need to add the documentation to each API. The documentation types supported in the API Publisher are as follows: In-line URL-based File-based Please refer [1] for more information regarding this.  If your requirement is to add a generic guide to the store unfortunately this is something not possible at the moment.  [1] https://docs.wso2.com/display/ APICloud/Add+API+Documentation

Sometimes, you may require to access your tenant by WSO2 cloud team, to investigate a issue, do some configurations changes on behalf of you, etc... This blog will say how you can allow WSO2 cloud team to access your tenant. 1. Go to cloud organization management portal: https://cloudmgt.cloud.wso2. com/cloudmgt/site/pages/ organization.jag 2. Click on check box (Allow Access to WSO2 Support) inline with your tenant name Later you can remove it clicking on the check box agina.