The error information for Okta can be viewed on the Druva Console or from the logs folder.
To view the errors and logs, follow these steps:
Log in to the Druva Cloud Console.
Click on the hamburger button and then navigate Okta.
Go to Jobs> click on Job ID> Download Logs.
Error references accessible from Druva Console
Invalid credentials
Error Message: Invalid credentials
Error Description: Okta rejected the client at the token endpoint. Sample log: Okta token request rejected error_code=invalid_client/ Client authentication failed.
Error Resolution:
Confirm that your Okta Client ID and Client Secret (or JWK key) are copied correctly and valid.
Try authorizing again.
If the issue persists, contact Druva support for further assistance.
Error references accessible from the Okta logs folder
Could not connect to Okta domain
Error Message: Could not connect to Okta domain
Error Description: DNS, TLS, or network failed before Okta responded. Sample log: Could not connect to Okta domain: dev-123.okta.com, error=Failed to establish a new connection.
Error Resolution:
Verify that the Okta domain is correct and accessible.
Check DNS, firewall, proxy, and network settings.
Try the operation again.
Request timed out - Okta server did not respond
Error Message: Request timed out - Okta server did not respond
Error Description: The token call exceeded 30 seconds. Sample log: Request timed out for Okta domain: dev-123.okta.com.
Error Resolution:
Wait a few moments and try again.
Check the Okta service status and network connectivity.
If the issue is not related to network connectivity, collect the relevant logs and contact Druva support for further assistance.
Request error
Error Message: Request error
Error Description: The HTTP client failed for a reason other than connect, timeout, or invalid URL. Sample log: Request error for Okta domain: dev-123.okta.com, error=HTTPSConnectionPool.
Error Resolution:
Wait a few moments and try again.
If the issue persists, collect the relevant logs and contact Druva support for further assistance.
Failed to commit backup: Not all objects are committed
Error Message: Failed to commit backup: Not all objects are committed
Error Description: This error occurs when a backup completes only partially.
Error Resolution:
Wait for the next scheduled backup or initiate a manual backup to allow the remaining items to complete.
If the error persists following the subsequent backup, contact Druva Support.
OAuth2 token request failed / Failed to get OAuth2 token via JWT
Error Message: OAuth2 token request failed / Failed to get OAuth2 token via JWT
Error Description: Okta refused the client-credentials token request. The backup cannot start for that tenant.
Error Resolution:
Verify that the Okta application is active and review its Client ID, Client Secret (or JWK key), and assigned scopes.
If the application is inactive or deleted, recreate it and re-authorize through the Druva console.