We are using OAuth to connect to Confluence and we have granted the scopes folder:read etc. however when we call the accessible-resources endpoint we do not see any of the folder scopes. Further when we try to use folder endpoints we get 401 errors.
some more info:
-
I have granted the scopes through my oauth application at the Developer console and can confirm that they show up both in the Permissions as well as under the Authorization tab.
-
I have tried this in Go, JS, and via curl.
-
I am trying to hit the /rest/api/content?type=folder. So I have tried to add the read:confluence-content.all scope as well as the read:folder:confluence and neither have worked. confluence-content.all at least will return when I call accessible-resources
-
I have looked this up endlessly. I was able to get it to work with basic auth using api key a couple weeks ago. If it isn’t supported with OAuth that should be documented. And here is why I am using the V1 endpoint: https://jira.atlassian.com/browse/CONFCLOUD-80566?jql=project%3DCONFCLOUD%20AND%20type%3DSuggestion%20AND%20statusCategory!%3DDone%20and%20text%20~%20"rest%20api%20folders"
Are V1 folder listing endpoints compatible with OAuth or do I need to use basic auth?
What is the timeline on a v2 list folders endpoint?
What is the recommended strategy for listing a full confluence space → folder → page hierarchy?