While the previous two releases focused on enhancing our Ozone partner experiences in a major way, we have something for the rest of our users as well for this month’s combined release of 1.2.4 and 1.2.5!

The Ozone platform would be seeing enhancements in terms of its plugins, minor front-end changes for better context, fixes for login flows where gaps were reported, and much more. In case you would like to know what we had to say for the month of September, you can read it here. Details follow:

1. Secured Ozone Installation From Private Registry:

Enabled by Harbor, the Ozone private registry can be used for the installation of Ozone by enterprises rather than connecting to a public registry which could be a potential security vulnerability. Ozone serves images from this private registry which can help enterprises to satisfy their compliance requirements when they onboard Ozone. 

2. CORS Plugin for SaaS Enabled by Default:

Cross-Origin Resource Sharing as the name suggests, lets applications loaded on one domain refer to resources that are present on another domain. This helps build rich web applications that can freely utilize resources distributed across domains without much constraints. 

Cross-origin resource sharing (CORS) can now be added easily to a Service and a Route using the Kong plugin which has been enabled for both the Ozone partners and SaaS users. 

3. ADB2C Login for Ozone Partner Accounts:

Azure Active Directory B2C (Azure AD B2C) is an identity management service that enables custom control of how your customers sign up, sign in, and manage their profiles when signing up or logging into mobile or web applications. 

While ADB2C was made default for Ozone partners in the last release, we have extended the same to the end-user accounts that are created by our partners in this release. The user sign-up/login processes are now streamlined where usernames and passwords are no longer required. 

Fixes

• SaaS users reported intermittent issues in the form of HTTP responses while signing up which has now been taken care of

• Fixed SaaS signup issues for pre-existing users post their SaaS upgrades

• Adding detailed labels for better contextual RBAC controls on what a user role does

• Added a CTA “Add to project” for clearer workflow on the empty state screen for clusters

• Toggling back to active clusters caused the archived clusters to change state which has now been fixed