# Confluence connector: non-existant permissions **URL:** \ **Category:** Elastic Search\ **Tags:** elastic-workplace-search\ **Created:** [March 2, 2022, 5:46pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656 "2022-03-02T17:46:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Robin\_Vanderschueren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_vanderschueren/32/102370_2.png) [@Robin\_Vanderschueren](https://discuss.elastic.co/u/Robin_Vanderschueren)\ **Post date:** [March 2, 2022, 5:46pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/1 "2022-03-02T17:46:53Z")
I'm trying to connect confluence to Workplace search but it seems that the permissions do not match the available permissions for the confluence API. I added "similar" permissions but receive the following error: `add the following scopes to the *Confluence API* : search:confluence, read:confluence-props, read:confluence-space.summary, read:confluence-content.summary, read:confluence-content.all, read:confluence-user, readonly:content.attachment:confluence.` When I try to add search:confluence (for example) it is not in the list of available permissions. ![Screenshot from 2022-03-02 11-46-03](https://us1.discourse-cdn.com/elastic/original/3X/f/1/f10d612348b4a6815ff3b74460147163578b2e68.png) Is this a bug? ---
**Author:** ![Robin\_Vanderschueren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_vanderschueren/32/102370_2.png) [@Robin\_Vanderschueren](https://discuss.elastic.co/u/Robin_Vanderschueren)\ **Post date:** [March 2, 2022, 5:49pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/2 "2022-03-02T17:49:55Z")
> **[Action required: Update scopes for Forge and OAuth 2.0 (3LO) apps](https://community.developer.atlassian.com/t/action-required-update-scopes-for-forge-and-oauth-2-0-3lo-apps/53299)** > > Hi, I am Julia Daehne, Ecosystem Product Manager at Atlassian. One of my main focus areas is app security which we know is a big requirement for our existing Cloud customers, and those who are still planning to move to Cloud. What’s changing? We... It seems that the scopes are deprecated. ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [March 2, 2022, 8:44pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/3 "2022-03-02T20:44:09Z")
@Robin_Vanderschueren This is odd. In the Atlassian Dev Community post you linked, I didn't see anything specifically saying they were removing `search:confluence`. Did I miss something? I do see that it is still listed on their official documentation of [Confluence OAuth2 scopes](https://developer.atlassian.com/cloud/confluence/scopes-for-oauth-2-3LO-and-forge-apps/): > `search:confluence` > > Search Confluence content and space summaries > > Search Confluence. Note, APIs using this scope may also return data allowed by read:confluence-space.summary and read:confluence-content.summary. However, this scope is not a substitute for read:confluence-space.summary or read:confluence-content.summary. if this is not showing up for you, I'd suggest that you first file a support request with Atlassian, as, from what I'm reading, it's still the expected and documented behavior to use `search:confluence`. However, we've definitely had a few instances this year with Atlassian making sudden changes underneath us, so if they respond by removing this from their documentation, we will make a corresponding bugfix. ---
**Author:** ![Robin\_Vanderschueren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_vanderschueren/32/102370_2.png) [@Robin\_Vanderschueren](https://discuss.elastic.co/u/Robin_Vanderschueren)\ **Post date:** [March 2, 2022, 10:18pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/4 "2022-03-02T22:18:55Z")
Thanks for the quick response @Sean_Story I'm checking with them now. ---
**Author:** ![Robin\_Vanderschueren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_vanderschueren/32/102370_2.png) [@Robin\_Vanderschueren](https://discuss.elastic.co/u/Robin_Vanderschueren)\ **Post date:** [March 2, 2022, 10:36pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/5 "2022-03-02T22:36:37Z")
I've looked into it and the deprecated scopes are not available anymore. Where can I request this to be updated with Elastic Workspace Search? ---
**Author:** ![Robin\_Vanderschueren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_vanderschueren/32/102370_2.png) [@Robin\_Vanderschueren](https://discuss.elastic.co/u/Robin_Vanderschueren)\ **Post date:** [March 2, 2022, 10:36pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/6 "2022-03-02T22:36:57Z")
This of course makes implementing the confluence connection impossible for new clients. ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [March 3, 2022, 11:29pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/7 "2022-03-03T23:29:45Z")
> [@Robin\_Vanderschueren](#): > > This of course makes implementing the confluence connection impossible for new clients. ☹ Yep. I'm sorry you're hitting this. I hope you express to Atlassian how impactful this is to your time and efforts. > [@Robin\_Vanderschueren](#): > > Where can I request this to be updated with Elastic Workspace Search? I've gotten it filed, and our team will be taking a look as soon as we can. Unfortunately, unless Atlassian rolls back this breaking change, you will be blocked until we can release a fix. In the mean time, we have added this as a [Known Issue](https://www.elastic.co/guide/en/workplace-search/master/workplace-search-confluence-cloud-connector.html#confluence-cloud-known-issues), and we've also filed a support ticket with Atlassian. ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [March 3, 2022, 11:31pm UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/8 "2022-03-03T23:31:20Z")
Oh, and thank you for reporting this. I regret that you had to encounter this issue, but we do appreciate your report of the issue. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 31, 2022, 2:48am UTC](https://discuss.elastic.co/t/confluence-connector-non-existant-permissions/298656/9 "2022-10-31T02:48:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.