Maverics console release notes
For older release notes, see the release notes archive.
2024-10-24: SAML Provider Issuer URL Override
The Orchestrator URL field defines default endpoints that are generated for OIDC and SAML provider settings. You can now override the issuer URL used when using the Orchestrator as a SAML provider.
2024-10-23: Ubuntu support, improved SSO error handling
Orchestrator is now available on Ubuntu
You can now download Orchestrator releases for Ubuntu from the Environments page.
Resolved issues
- For Enterprise SSO setup, the Maverics console requires standard OIDC claims of user, profile, and email. If this claim is missing on the session, the error shown in the UI will now indicate which claims are missing. See our documentation.
2024-10-17: UK region, logger settings
UK region is now available
You can now sign up at https://uk.maverics.strata.io
Logger settings
You can now set logger settings in the environments page.
Resolved issue
- Resolved an issue where duplicated identity fabrics were listed on user flow drop down menus.
2024-10-08: Configure orchestrator health endpoint
The orchestrator exposes a /status
endpoint, which can be polled by an external service to determine health. A live orchestrator will return an HTTP 200 when a GET request is made to the status endpoint. By default this is served by /status
.
In this release, you can now customize this endpoint so it does not clash with other routes in use.
To customize the endpoint, edit an environment and go to the Orchestrator Settings section. You can set the Health check endpoint here.
2024-10-02: Deployment enhancements, bug fixes, and refactoring
Deployments
You can now remove user flows from an environment at the deploy preview step. With this capability, you can selectively remove user flows from the environment, update the deploy preview, and show a diff of what has been removed.
Resolved issues
- Fixed an issue where API app type name updates would not persist.
- PenTest - 5.3. WEB-M1: Cross-Site Scripting - In this case stored XSS was identified within the filename parameter within the “Service Extensions” and “Assets” section of the application where users could write short Golang programs that hook into extension points within the orchestrator.