In case you hadn't heard, we will be upgrading our platform (Centrify Identity Service and Centrify Privilege Service) to version 16.2 this weekend (Sunday, February 28th). The complete list of new features is available in the release notes, but as always I will tell you about my favorite new features here:
Redesign of Settings Menu
The Settings menu has always been the place to configure tenant-wide settings. When we first started out with the product we had just a few menu items so a list of those settings was perfectly acceptable. Over time, our product has become much more robust and the settings menu kept growing. This has been largely fine for our installed base as the growth was incremental and well explained. However, this created a fairly daunting interface to learn for new administrators. I'm happy to say we've cleaned up the clutter and have created an organized settings menu with like settings grouped into the following logical categories:
The new UI is not only more aesthetically pleasing, but also includes some new capabilities. Specifically, we took this opportunity to move the Setting that enables Mobile Device Management to the Policy engine. This is significant as this enables organizations to allow a mixed use case where some devices can be enrolled with our service for MDM while others can be enrolled for SSO only.
Many customers have told us that they love our MFA solution. They love that it can be used for authentication into the portal, and/or for step-up authentication with specific apps. They further love that this same solution can be used for strong auth for their servers and privilege elevation through Centrify Server Suite and Centrify Privilege Service. These customers have told us that they want to use a single MFA solution wherever they are using MFA. Typically, these customers have asked us to extend our MFA to their VPNs so that Centrify could be the single solution used for MFA throughout their organization.
With 16.2, our Cloud Connector can serve as a RADIUS server allowing us to extend our MFA to any RADIUS client (e.g. a VPN)!
Truth be told, many of the customers who asked us to extend our MFA solution to their VPNs started out by asking if they could use their existing OATH-based OTP solution instead of the Centrify Mobile Authenticator for MFA. This made perfect sense to us, so we enabled this too. We understand the benefits of standardizing on one solution. We believe implementing MFA is a best-practice that all companies should use and we want to make that easy for our customers. Adding OATH support makes it easy for companies who have already standardized on a 3rd party OTP tool to leverage that investment.
We hope you enjoy these new features and look forward to hearing your feedback!