June 28, 2025
Feature
Securing failsafe login experience
Starting June 28, 2025, Druva has updated the sign-in experience for accounts with Single Sign-On (SSO) configured. Previously, Cloud Administrators could use the failsafe login option (username and password) as an alternative to signing in via their SSO provider. As part of this change, the login experience is now streamlined to use SSO exclusively. If you require access via the failsafe method, please contact Druva support for assistance.
Legal Hold Admins can continue to access their accounts using the Sign in as a Legal Hold Admin link available on the login page.
This update helps customers ensure that all administrators consistently use SSO for authentication, while also protecting the environment by preventing potential misuse of the failsafe password-based login by unauthorized users.
Introducing an updated integration center with Webhooks
We're excited to announce our refreshed integration center.
The new integration center brings together:
Out of the box integrations that Druva supports
A new home for API credentials
A brand new mechanism to integrate external services via webhooks
This is our attempt to bring all external integrations under a single roof. Earlier, API credentials lived under manage administrators section. But we think that each mechanism to connect an external service with our platform should stay in one place.
We're also excited to introduce webhooks as a new way to connect an external service with our platform. Now, you can specify a webhook URL, and we will post events to that URL in real time. To learn more about webhooks, see Use webhooks to integrate third party services with Druva.
March 22, 2025
Feature
Administrator Management with AD/LDAP
The Administrator management using AD/LDAP is now generally available (GA).
With this functionality, the integration with AD/LDAP Connectors and AD Accounts is centralized to manage Druva administrators efficiently by the DCP administrators.
The Administrator management feature uses your existing Active Directory (AD) or Lightweight Directory Access Protocol (LDAP) integration and simplifies managing Druva administrators within the Druva Cloud Platform (DCP).
Benefits:
Simplified Administrator Management: Organizations using AD/LDAP for user management can now effortlessly manage Druva administrators as well.
Improved Efficiency: Leverage your existing AD/LDAP integration for centralized administration of Druva users and administrators.
What's New?
New AD/LDAP Connector: A new version of the AD/LDAP Connector is included to support Administrator Management functionality.
Updated Settings Location: Previously, AD/LDAP Connector and Account settings resided in the "End Points and SaaS Apps Settings" page. These settings have been relocated to the "Druva Cloud Settings" section within the DCP console.Upgraded Administrator Permissions: Upgrading of AD/LDAP Connectors is now an exclusive privilege of Druva Cloud Administrators.
Action Required: Upgrade all existing AD/LDAP Connectors to the new version. This upgrade is necessary to grant the required permissions to inSync and DCP administrators to modify mappings and configurations.
❗ Important
Existing AD mappings created for user management will continue to function. However, to allow inSync & DCP Administrators to modify mappings and related configurations, DCP Administrators must upgrade all existing AD/LDAP connectors.
For more information, see, Upgrade AD/LDAP Connectors.
Introducing Inactive Administrator Policy for administrator account management
We have introduced the Inactive Administrator Policy designed to enhance administrator account management.
Key highlights:
Druva Cloud Administrators can now set a specific inactivity period for administrator accounts.
Administrator accounts that remain inactive beyond the defined period will be automatically disabled.
This feature helps ensure that only active administrators have access to the Druva environment, effectively managing the lifecycle of administrator accounts and minimizing exposure to potential attacks.
For more information, see Configure Inactive Administrator Policy.