Cloud Blog

Swapping version and context in API URLs

By default, APIs published in WSO2 API Cloud get URLs like http://{base-gateway-URL}/{API context}/{API version}/{API resources and parameters}. For example, if the custom URL that you assigned to your gateway is api.my.domain, you might get something like http://api.my.domain/stats/1.0/countries/us.

But what if you want to place the version number first and have something like http://api.my.domain/1.0/stats/countries/us instead? This is trivial too. Simply type {version}/stats (or whatever your API context is) instead of just stats as the context on the first step of API creation:

And you can remove the version number altogether by selecting the Make this the Default Version checkbox on the 3rd step of API creation:

WSO2 API Cloud is a powerful API management platform that allows you to easily create the exact API program you need!

Multi-file upload for ESB projects

Integration projects can be complex and include multiple services.

In the world of WSO2 ESB, these services are created and uploaded as CAR files.

We have rolled out a nice little Integration Cloud improvement that makes hosting such projects easier. Any ESB app in Integration Cloud can now have multiple CAR files uploaded and running.

When you create a new ESB app or a new version of an existing app in Integration Cloud and you have multiple CAR files, simply browse to each of them one at a time, and the system will get all of them uploaded and added to the runtime:

When you scale this application to multiple instances, each new instance automatically gets all the CAR files that you uploaded.

And you also save money and compute resources because the same ESB instances are reused across the projects.

Happy integrations!

Identity Cloud Launched

I am happy to announce that we have launched the free beta of WSO2 Identity Cloud.

WSO2 Identity Cloud is based on the open-source WSO2 Identity Server product. It helps companies set up single sign-on (SSO) from their local enterprise directories to web applications.

You also get a brandable application catalog page for easy application discovery.

As result:

  • You improve your corporate security:
    • Users no longer access web apps when their enterprise credentials are disabled.
    • You can see who accesses which applications.
    • Your password security is enforced across all applications.
  • You make your employees more productive:
    • They no longer have to maintain multiple passwords,
    • They can find the applications available to them.
  • You can reduce costs:
    • Reports let you see which applications are actually in use by whom.

Here’s how you can get started:

1. Log into Identity Cloud,

2. Download the agent to connect the cloud to your local user store,

3. Add applications to the catalog (with predefined templates, uploaded definition files, or manual settings):

That’s it! Your users can access the applications directly or via a nice application catalog page:

See more information in Identity Cloud documentation and let us know what you think!

Categories

Recent Posts

Most Popular Posts