I am attempting to authorize the Atlassian Rovo Agent inside an Enterprise Slack Grid workspace (://slack.com).
The user OAuth redirect loop stalls on ://atlassian.com, resulting in a blank page. Forcing the authorization flow within an Incognito window exposes the underlying API rejection text: scope_not_allowed_on_enterprise.
It appears the app payload is requesting a forbidden global user/identity scope that cannot be installed at the Enterprise Grid organization tier. Can the development team review the required scopes called during individual workspace mapping?
Hello @Tarun Singh
Since you are on Enterprise, I would definitely raise this with Atlassian Support rather than troubleshooting it only through Community.
If you cannot open the ticket yourself, ask your organization admin, site admin, technical contact, or billing admin to raise it on your behalf. This looks like an Enterprise Grid / Rovo Slack OAuth scope issue, and Atlassian will need backend/app-side visibility to confirm what is happening.
We are just users like you.
Best,
Arkadiusz 🤠 ☀️
Hi @Arkadiusz Wroblewski
This is helpful. Appreciate your input. I will reach out to our organization admin to get an official Atlassian Support ticket opened for this OAuth scope issue.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.