Q: Does taking backups impact my Okta API rate limits or slow down user logins?
A: No, the integration performs automatic, zero-impact backups that are guaranteed to keep data up-to-date without slowing down Okta or hitting your API limits.
Q: What administrative roles are required to set up the Druva for Okta integration?
A: The Druva application requires Okta Super Admin privileges to grant administrative API scopes and authorize the OAuth connection, in addition to User Druva Cloud Admin privileges to enable the integration in the Druva Console.
Q: How does Druva handle user passwords during a restore?
A: Okta does not allow the extraction of hashed passwords, meaning Druva cannot restore a user's original password. Instead, when a user is restored, their status is set to 'Staged' and they will receive an activation email to create a new password.
Q: What happens if I try to restore a user or group that already exists in Okta?
A: You can choose how the system handles conflicts using the "On Conflict" setting. You can choose to Skip (leave existing data unchanged), Overwrite (replace existing Okta records with the backup version), or Merge (combine the backup data with the existing record to fill missing attributes).
Q: Can I restore one specific group and one specific application at the same time?
A: No, granular selection across multiple categories is not supported in a single job. If you perform a multi-item restore, you must restore the entire category (e.g., all groups and all applications).
Q: I’ve regenerated an expired Okta credential. How should I update it in the Druva console?
A: To update your credential, simply reauthorize the existing domain.