-
Bug
-
Resolution: Fixed
-
High
-
29
-
Minor
-
15
-
Issue Summary
3rd Party Add-ons stops working if default group isn't confluence-users
Steps to Reproduce (example with Slack, but same bug can happen with any other addons)
- In an instance with Slack integration enabled, create a new group - abc
- Grant this group the "default" status and add it to Confluence product access
- Remove product access and default status from confluence-users
Expected Results
Integration still works as expected.
Actual Results
The below error is observed.
Something went wrong while xxxxx. Please try again later or contact support.
Error code: UNEXPECTED_ERROR
Error ID: xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx
This happens because the Slack Integrations user (confluence-chats-integration@connect.atlassian.com) adds itself to confluence-users and atlassian-addons. Since none of those groups are granting it product access to Confluence, it doesn't work.
Workaround
Contact Support to add the system user (product member role) to your default group with the help of an internal script.
- causes
-
CONFCLOUD-69618 Error when integrating confluence with slack
- Closed
- is related to
-
MP-53 Add-on installation fails when there is no default access group set in the product access
- Closed
-
MIG-905 App user cannot access Space after migrating with CCMA
- Closed
-
CONFCLOUD-77485 App user missing product access
- Closed
-
CONFCLOUD-69755 Explanation of Confluence Connect app user permissions
- Gathering Interest
-
ECO-85 It should be documented how the connect app user and groups work and how changing default product access groups can break apps
- Gathering Interest
-
MIG-837 Apps can't access restricted content in Confluence Cloud
- Under Consideration
-
UAM-300 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
AC-2320 Loading...
-
DOCS-32831 Loading...