Guide to the set up of Okta as the OpenID Connect (OIDC) Identity provider for MuleSoft Anypoint organizations to use its OAuth 2.0 authorization server and access management capabilities to secure their APIs.
At the end of June, MuleSoft released an Anypoint Platform tool that I am so excited about, called the Anypoint Visualizer. As the name implies, the Visualizer provides visibility into your application network, giving you additional insight into your APIs, including:
One of the benefits of being a consultant is having the opportunity to work with a lot of different clients, many just beginning their journey with MuleSoft and API Led Enablement. In this article, I will share some of the observations and findings that I have seen that have enabled this journey to be more successful.
API Manager 2.x has support for environments which correspond to those defined within Anypoint Platform for the Runtime Manager (i.e. DEV, QA, PROD). This is an improvement over the 1.x version, which typically required the construction of version names to reflect an environment. With this enhanced functionality comes a bit of complexity during API deployment.
I've downloaded the latest Anypoint Studio(Version 7.1.2) to use on Ubuntu(18.04) and I wasn't able to view pop up dialog windows, for example, when clicking the Exchange button. This blocked me because of the several pop up dialogs you need to configure single components.
The batch scope within a MuleSoft application enables the ability to process a message as a batch, splitting the incoming payload into individual records to be processed. While the default values within this scope can be used, considerations around what these default values provide along with implications of these chosen values are explained within this article.
The batch scope configurations to be discussed are limited to just the General configurations. For reference, the default values for this configuration are shown below: