Cloud Blog

Single Sign-On into API Cloud UI

WSO2 API Cloud is a web-based API management suite but you can now also use your corporate identity system to log into its web user interfaces!

To configure the integration, click External Users on the Configure menu:

You can then select one of the two ways to integrate:

  1. Direct integration with your Identity Provider (IdP), or
  2. LDAP or Active Directory integration via WSO2 Identity Cloud.

Here’s a quick overview of how these work.

Integration with an Identity Provider (IdP)

If you already use an identity provider such as Shibboleth, Google Apps, or ADFS, simply pick the corresponding provider from the dropdown list and supply the additional parameters:

WSO2 API Cloud will then start using this IdP to get users authenticated into the Publisher, Admin, and API Store user interfaces:

See our documentation for more details: Configure an External Identity Provider for API Cloud Authentication.

LDAP or Active Directory integration via WSO2 Identity Cloud

In this case, you use WSO2 Identity Cloud agent to get your local directory server connected to WSO2 Cloud.

You then simply tell API Cloud which local groups need to be mapped to which roles in API Cloud: who will be able to publish the APIs, subscribe to them, and so on:

See this documentation for details:Configure an On-Premise User Store for API Cloud Authentication.

Single Sign-On (SSO) makes your API management easier to use and more secure. Try it today in WSO2 API Cloud.

API Cloud now also encrypts data at rest

Security is the cornerstone of successful cloud projects and API management is no exception.

We have for a long time implemented multiple layers of cloud security including among other things encryption of all data in motion, strict tenant separation, fully patched systems, extensive security training and policies for all WSO2 engineers running the cloud.

Today we are happy to announce that one more milestone has been reached in our security journey – data at rest (all the configuration data you create and store) in WSO2 API Cloud is now also encrypted.

What’s even better:

  • This includes not just the US, but also all the regional deployments of API Cloud,
  • There is no impact on your APIs performance (see the response times in our availability dashboard),
  • You don’t have to do anything or pay anything extra: the change is now live for all paying and trial customers.

This is just one of those examples of the service getting better and better all the time.

If you have any questions just contact us and we will be happy to help.

Move query parameters to REST path

Your API backend often does not match the desired frontend representation. For example, it might have extra parameters (such as API keys) that you do not want to expose and have some query parameters that you now want to just include in the REST path.

For example, you might want to do a transformation like shown in the picture below:

Today we will see how easy it is to do so with WSO2 API Cloud.

We will turn a pretty convoluted API from Marvel that looks like:
into something like my.api/hero/name.

1. First, we go to API Cloud and start designing the new API.

We create the API as usual, but in URL Pattern field, provide the parameter names that we want to have in the REST path in curly brackets – for example, {name} instead of name:

2. On the second step of the API creation wizard, we paste the backend URL and substitute the parts that we want to be taken from the input parameters with {uri.var.name_of_the_path_parameter}.  So

3. Now API gateway will automatically insert our name parameter into the backend URL and keep the other parameters intact. However, by default, it will still be adding our path parameter to the end of the backend URL too. With that, we risk invoking something like instead of the that we need.

Removing that trailing part of the URI is easy. We just need to pass the corresponding command to the gateway transformation engine.

Create a text file with the following text and save it as xml:

<sequence xmlns="" name="drop_uri_sequence" >
<property name="REST_URL_POSTFIX" scope="axis2" action="remove"/>

To upload the file: select the Enable Message Mediation checkbox, click the Upload In Flow button, and upload the xml file:

4. Now you can finish the API creation wizard and publish the API.

5. In API Store (Developer Portal), you can now subscribe to the new API and invoke it. As you can see, we now get the same results as the original API produces but with a much nicer and shorter invocation URL (which you can make even shorter by setting it as the default API version and using the custom URL functionality):

WSO2 API Cloud (and open source WSO2 API Manager) give you a powerful solution to make your APIs look exactly the way you need them.

How to synchronize new Salesforce leads to Google sheets and get Gmail notifications using WSO2 Connectors

WSO2 provides Connectors dedicated for the most popular business critical services that you will need such as SalesForce, Amazon, Twitter, Google, SAP &  Microsoft Dynamics. You can simply download the required connector from the WSO2 Connector Store and plug it into your integration flow with just a few clicks.

One such simple solution is exporting Salesforce leads to Google sheets. This lets you create your own Customer relationship management (CRM) system and a sales pipeline based on your email data. You can even use this information to send customized mailers to selected target groups.

Lets take a look at how you can use the Salesforce SOAP connector to get details of new leads use the Google Spreadsheet connector to add that information to a spreadsheet.


This is a pre-built solution. The  required artifacts can be downloaded via the WSO2 Store. *You can even take a look at the source code here. 

  1.  To customize this solution for your own salesforce account, google docs, you have to configure the salesforce and google docs accordingly and obtain the required credentials.
  2. You can download the sample json file with default values. Update the json file with the credentials extracted in above step.
  3. You can deploy the solution in Integration Cloud using the artifacts downloaded in step1 and the environment variable json file modified in step3.
  4. Finally, to test this scenario create a new lead in Salesforce.

Your spreadsheet gets updated with the information you provided when creating the new lead and an email notification will be generated.

You can extend this solution by using  the WSO2 Developer Studio . The graphical interface of the Developer Studio makes it easier and faster for you to modify existing templates and customize to  your specific requirements.  

For a detailed step by step guide on how to integrate Salesforce leads to Google sheets visit the WSO2 Store! 


Faster ticket resolution through granting access to support team

We know that support experience can be frustrating when the engineer on the other side does not fully understand the exact issue that you are facing and you get into the long back and forth with questions, answers, and screenshots.

There is now a better way! When creating a support ticket, you can now simply select the Allow Access to WSO2 Support checkbox and the engineer that gets your ticket assigned will be able to securely access your WSO2 deployment and troubleshoot the issue:

This new feature radically shortens the resolution time and gets your going with your project faster. And once the ticket is resolved, you can simply go to the Organization screen (in the 9-dot menu) and revoke the access.



Recent Posts

Most Popular Posts