Release Notes 2024.2
Bug Fixes
The changes to SAML in 2024.1 have led to problems for some customers. The adaptations to SAML are now fully backwards compatible with this version.
If a user of an internal identity provider did not have a login name, the name of the user was not displayed in "Resources" -> "Internal Identity Provider".
New Features
The Gateway Manager now uses the new Graphman interface. Graphman has not yet been fully finalised by Broadcom and therefore Restman will continue to be used for everything else that Graphman cannot yet do.
Loading the resources from the node is significantly faster thanks to the modern GraphQL interface using JSON.
Graphman must first be activated.
APIIDA API Control Plane
The metrics of the APIs are now forwarded to the Agent.
The handling of deploying plans and API keys has been improved and is now less error-prone.
The "Skip Indexing" for each migration can now be globally preselected in the configuration.
If "Skip Indexing" is not activated, all resources of each node are updated before a migration. If only the gateway manager makes changes to the nodes, you know that the resources are up-to-date or the resources are updated periodically, it is not necessary to index the nodes.
In "Resources", after selecting a resource, you can now view the XML or JSON data of the resource by clicking on the eye icon next to "Base Data".
Changes
Performance Improvements
The loading of resources from the nodes, also known as indexing, no longer takes place one node at a time but in parallel. The view has also been adapted accordingly.
This happens, for example, in "Resources" -> "Reload Resources" when several or all nodes are selected.
When preparing the migration without skip indexing, all targets and the source are indexed in parallel.
With "Discover APIs" in "APIs", only the resources required to register a new API are reloaded. This means folders, services and policies.
Confirming all alarms thrown by the Gateway Manager is now much more efficient. In addition, there is now a button in "Alarms (bell icon top right)" -> "Click here to see all alarms" -> "All", which resets all alarms and the status of each node and each API.
The timeout for Restman and Graphman can now be configured in "Configuration" => "General". This is particularly interesting if a large number of resources are migrated. Restman can sometimes need several minutes for a response.