Troubleshooting

This topic provides information to help you resolve potential issues that you might encounter when using the integration of CrowdStrike Falcon Fusion SOAR with Secret Server.

Issue	Possible Cause	Resolution
Authentication failure (401)	Incorrect username, password, or Grant Type	Verify that the credentials match the API user created in Creating an Application Account in Secret Server. Confirm that Grant Type is set to password.
Connection timeout	Incorrect Tenant URL or network issue	Verify the Tenant URL format. Ensure that the Secret Server Cloud instance is reachable.
"Update User" action fails	Unlimited Admin Mode is not enabled.	Enable Unlimited Admin Mode. For details, see (Optional) Enabling Action-Specific Settings.
"Sync AD" action fails	Directory Services is not enabled	Enable Directory Services. For details, see (Optional) Enabling Action-Specific Settings.
Insufficient permissions	The application account lacks the Administrator role.	Assign the Administrator role to the application account. For details, see Creating an Application Account in Secret Server.
Configuration saved in Falcon Content Library with errors	One or more required fields in the Delinea Secret Server SOAR Actions app configuration were entered incorrectly.	Set Grant Type to password. Make sure that Tenant URL is the full Secret Server Cloud URL (for example, `https://<tenant>.secretservercloud.com`). Check that you provided the correct credentials the application account in Secret Server in Username and Password and confirm that the application account exists in Secret Server and that it is not disabled. Save the configuration again and check for inline field validation errors before saving.
The "List Users" action does not return user data from Secret Server.	The application account in Secret Server does not have the Administrator role. Unlimited Admin Mode is not enabled.	Assign the Administrator role to the application account. For details, see Creating an Application Account in Secret Server. Enable Unlimited Admin Mode. For details, see (Optional) Enabling Action-Specific Settings.
The "Lookup Secrets" action does not return secrets from Secret Server.	The secrets being queried are not within the application account's accessible folder scope, or the search parameters passed to the action (such as search term, folder ID, or template filter) do not match any secrets visible to that account.	Verify that the application account (or its role) has been granted at least View access on the folders containing the target secrets. Navigate to the folder in Secret Server, go to its Security tab, and confirm that the application account appears with appropriate permissions. Double-check the search parameters being passed in the Falcon workflow action. Ensure that the secret name, folder, or template filters are correct and not overly restrictive.
“List Secret Folders" does not return folder structure.	The application account configured in the Falcon integration has not been granted any folder-level permissions in Secret Server. A secondary cause could be that the Tenant URL in the Falcon configuration is pointing to an incorrect or unreachable Secret Server instance.	Verify folder permissions for the application account. In Secret Server, navigate to the root folder (or the top-level folders that should be visible), open the folder's Security tab, and confirm that the application account or its assigned role has at least View access. Enable folder permission inheritance on child folders so the account can see the full tree beneath any folder that it is granted access to. Check the Tenant URL in the Falcon configuration. Navigate to Fusion SOAR > Content Library > Delinea Secret Server SOAR Actions > Configure and confirm that the Tenant URL exactly matches your Secret Server Cloud URL (for example, `https://<tenant>.secretservercloud.com`). An incorrect URL that still resolves to a valid Secret Server instance would authenticate successfully but return data for the wrong tenant.
The workflow execution log shows authentication failures.	Authentication failures in the execution log indicate that the OAuth token request to Secret Server is being rejected. The most common causes are: The Grant Type is not exactly password. Even a capitalization difference (Password vs password) can cause the token endpoint to reject the request. The Username or Password stored in the Falcon configuration has changed in Secret Server (for example, a password rotation occurred), but the Falcon configuration was not updated. The application account in Secret Server has been disabled, locked out (due to failed login attempts), or has expired. The Tenant URL is incorrect, causing requests to reach the wrong endpoint or fail DNS resolution entirely.	Navigate to Content Library > Delinea Secret Server SOAR Actions > Configure in Falcon and edit the configuration. Re-enter the password to ensure that it matches what is currently set in Secret Server. In Secret Server, navigate to Access > Users, find the application account, and confirm that it is enabled and not locked. Reset the password if needed and provide it back to the Falcon configuration. Confirm that the Tenant URL exactly matches the Secret Server Cloud URL (no trailing slashes, correct subdomain).