Confluence Connection Fails
aprity connects to Atlassian Confluence via OAuth to publish documentation to your wiki. If the connection fails during setup or stops working after initial configuration, this guide covers the most common causes.
Confluence integration is available on Enterprise plans only. If you are on a different plan, the Confluence connector will not be available.
Common causes
Popup blocked by browser
The Confluence OAuth flow opens in a popup window. If your browser blocks the popup, the authorization flow cannot complete.
Symptoms:
- Clicking Connect on the Confluence card does nothing or briefly flashes.
- The browser shows a "popup blocked" indicator in the address bar.
Solution:
- Allow popups for your Salesforce domain in your browser settings.
- In most browsers, click the popup-blocked icon in the address bar and select Always allow popups from this site.
- Return to the Connectors tab in aprity and click Connect again.
Third-party app access disabled in Atlassian
Atlassian workspace administrators can restrict which third-party apps are allowed to connect via OAuth. If this setting is disabled, aprity cannot receive authorization.
Symptoms:
- The popup opens and redirects to Atlassian, but you see an error message about third-party access being restricted.
- The authorization page does not load or shows an "access denied" message.
Solution:
- Ask your Atlassian workspace administrator to go to admin.atlassian.com.
- Navigate to Settings > Security > API tokens or Settings > Security > Third-party apps.
- Ensure that third-party app access via OAuth is enabled.
- Retry the connection from the aprity Connectors tab.
Changes to Atlassian admin settings may take a few minutes to propagate. Wait and retry if the connection still fails immediately after enabling third-party access.
OAuth token expired or revoked
If Confluence was previously connected but has stopped working, the OAuth token may have expired or been revoked.
Symptoms:
- The Confluence card shows Connected but publishing fails.
- You see errors mentioning "unauthorized" or "token expired" when attempting to publish.
Solution:
- In the aprity app, go to the Connectors tab.
- Click Disconnect on the Confluence card.
- Wait a few seconds, then click Connect again.
- Complete the OAuth authorization flow to issue a new token.
Wrong Atlassian account
If you have multiple Atlassian accounts (for example, a personal account and a work account), you may have authorized with the wrong one.
Symptoms:
- Connection succeeds but the expected Confluence spaces are not listed.
- Publishing fails with a "space not found" or "permission denied" error.
Solution:
- Disconnect the current Confluence connection.
- Log out of Atlassian in your browser, or use an incognito/private window.
- Reconnect from the aprity Connectors tab, signing in with the correct Atlassian account.
Verifying the connection
After resolving the issue:
- The Confluence card on the Connectors tab should show Connected.
- Try selecting a Confluence Space -- the dropdown should list your available spaces.
- Run a test publish from a completed scan to confirm end-to-end functionality.
Still not working?
If none of the above resolves the issue:
- Note the error message displayed in the aprity app or browser console.
- Confirm which Atlassian account and Confluence instance you are trying to connect to.
- Contact support at support@aprity.ai with these details.