Troubleshooting

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

Problem	Likely Cause	Resolution
Event Subscription URL verification fails	Firewall or proxy blocking Slack's outbound request to Secret Server.	Ensure Secret Server is reachable from the internet. Check firewall rules for Slack's IP ranges. Verify the URL uses HTTPS.
Events not received after successful URL verification	App installed by a Secret Server cloudadmin or Slack Org Admin account.	Reinstall the app using a regular workspace member account. See the Known Issues section below.
Install to Workspace button is grayed out or missing	Slack app management policy requires admin approval.	Contact your Slack Org Admin to approve the app, or request a temporary exception for custom app installation.
Slack UI does not match documented process	Customer is on Business+ or Enterprise Grid (different admin interface).	The core settings (OAuth, Events, Interactivity) are in the same locations at api.slack.com/apps. The differences are in installation flow and approval process.
Bot token generates but events still fail	The installing user lacks channel visibility or Enterprise Grid blocks bot interactions for the installer's role.	Verify the installing user is a regular member with channel access. Check Enterprise Grid admin policies for bot restrictions.
Secret Search shortcut not appearing in Slack	Shortcut not configured, or app needs reinstall after changes.	Verify the Global Shortcut Secret Search with callback ID secretsearch is configured. After any scope or config changes, reinstall the app.
Users get errors when signing into the bot	Secret Server URL not reachable from user's browser, or SSL certificate issue.	Ensure the Secret Server URL is accessible via HTTPS with a valid certificate. For on-premises, verify the external domain DNS is configured per prerequisites.

Known Issues

Event Subscriptions Fail with Admin Account

Symptoms

• The Slack app is installed and configured following the documented process.

• Event Subscriptions (request URL verification, bot events) do not work or fail silently.

• The Slack app was installed by an Org Admin account (for example, cloudadmin@company.com).

• When the same app is reinstalled by a regular workspace member, events work correctly.

Root Cause

This is a Slack platform behavior, not a Delinea defect. Bot tokens are generated in Slack during app installation and are tied to the installing user’s workspace context. On Slack Business+ and Enterprise Grid, Org Admin accounts (cloudadmin) typically have restrictions that cause Event Subscription failures:

Factor	Impact on Integration
Restricted channel membership	Org Admins often cannot participate in regular workspace channels. Events are only delivered for channels visible to the app's installation context.
Enterprise Grid security policies	Admin identities are frequently blocked from bot interactions as a security measure.
Token tied to admin context	The bot's OAuth token inherits the admin's restricted scope. Events depend on what permissions and visibility the installer has.
No channel visibility	If the admin account cannot see a channel, the bot will not receive events from that channel.

Resolution

The Slack app must be installed (or reinstalled) by a regular Workspace Owner or member account, not by a Slack Org Admin or Secret Server cloudadmin.

Step-by-Step Fix:

1. Identify a regular workspace owner or member who has normal channel membership and visibility in the target Slack workspace. This person must be a Workspace Owner (not an Org Admin on Enterprise Grid).

2. If the app is already installed, uninstall it from the workspace first. Go to the Slack App Directory in your workspace, find the Secret Server Bot, and remove it.

3. Have the identified workspace member log into https://api.slack.com/apps and navigate to the Secret Server Bot app.

4. Reinstall the app to the workspace by clicking Install App > Install to Workspace. This generates a new Bot User OAuth Access Token.

5. Copy the new Bot User OAuth Access Token into the Secret Server Slack Integration settings (Settings > Slack Integration > Bot Token field).

6. Check the Event Subscriptions page in the Slack App config to verify Event Subscriptions are working. The Request URL should show Verified with a green checkmark.