Hello Experts,
I am recently exploring confluence REST APIs. I was trying examples at https://developer.atlassian.com/server/confluence/confluence-rest-api-examples/
So I created a my free sample Space & Confluence Page at Atlassian cloud https://userid.atlassian.net/
When I tried using curl GET example I am getting
{"message": "Current user not permitted to use Confluence","statusCode": 403}
I referred all the examples & Suggestions given at below links but couldn't able to figure out the issue. If you could help me out in understanding and showing me the direction that would be great.
https://community.atlassian.com/t5/Confluence-questions/Confluence-Cloud-REST-API-quot-message-quot-quot-Current-user/qaq-p/1566379
https://community.developer.atlassian.com/t/current-user-not-permitted-to-use-confluence-error-when-getting-app-properties/38472
https://community.developer.atlassian.com/t/401-unauthorized-with-bearer-token-from-oauth/42561
Error step:
C:\Users\sent>curl -D- --ssl-no-revoke -u <userid>:<Api token> -X GET -H "Content-Type: application/json" https://userid.atlassian.net/wiki/rest/api/content/<pageno>HTTP/1.1 403 ForbiddenServer: AtlassianProxy/1.19.3.1vary: Accept-Encodingcache-control: no-cache, no-store, must-revalidateContent-Type: application/jsonStrict-Transport-Security: max-age=315360000; includeSubDomains; preloadDate: Thu, 27 Jan 2022 20:28:40 GMTATL-TraceId: 08513d1914924dedexpires: Thu, 01 Jan 1970 00:00:00 GMTX-XSS-Protection: 1; mode=blockTransfer-Encoding: chunkedx-envoy-upstream-service-time: 42X-Content-Type-Options: nosniffATL-Confluence-Via: h:confluence-prod-us-7-3.prod.atl-paas.netExpect-CT: report-uri="https://web-security-reports.services.atlassian.com/expect-ct-report/global-proxy", enforce, max-age=86400Connection: Keep-Alive
{"message":"Current user not permitted to use Confluence","statusCode":403}
Hi @Senthil Prasanth
Did you create a token from here
https://id.atlassian.com/manage-profile/security/api-tokens
And can you navigate to Confluence UI?
Let me know
Thanks
Hello @Pramodh M
Yes, I created a API token at https://id.atlassian.com/manage-profile/security/api-tokens
Thanks in Advance.
Could you please assist us here.
Thanks in Advance;
I just found it here. I also encountered a similar problem. The difference is that I can upload successfully using curl, but I try to send about 800m files in GitHub action (I'm waiting for pipeline to update some features to switch to bitbucket)
`{"message":"Current user not permitted to use Confluence","statusCode":403}`
Any suggestions?
I just faced the same problem, after digging a little bit in the suggested examples by @Pramodh M I found the solution that worked for me.
What you need to do is essentially just add an `Authorization` header with the following format:
`Authorization: Basic <base64 encoded token>`
Where the `<base64 encoded token>` should be generated by encoding the following string:
`your_email@domain.com:your_user_api_token` => Base64 encoding => `eW91cl9lbWFpbEBkb21haW4uY29tOnlvdXJfdXNlcl9hcGlfdG9rZW4=`
(Atlassian recommends this site for the encoding https://www.base64encode.net/)
Keep in mind, at first I could not make it work too, but then I remembered that my email was changed so I had to generate a new encoded token, following which the API call worked.
Hope this helps!
Regards,
Art Linkov
Same here.. Took 3 hours and cannot find a reason. I am the org owner but I cannot change the permission of a space.
This did my nut in until I realised that being logged into multiple Confluence accounts was causing the issue.I use my company email for day to day and my personal email to test my scripts before I use them in production.
As it turned out, even though I was logged into my personal account in the dev spaces, when I clicked the link from there, in settings, to create an API, the resultant settings page was under the work email. Long story short, see if when creating an API key you are logged into the correct account.
The Atlassian user should have access to Confluence app, the `View` and `Add` permissions in the space on it and the `Can edit` permission on the page in that space. Also, you need to create an API token as the password won't work. After doing all of this, it worked for me.
It looks like you're new here. Sign in or register to get started.