-
Suggestion
-
Resolution: Duplicate
-
None
-
1
-
Problem Statement
- Attempts to configure service accounts with the necessary API scopes are unsuccessful for specific endpoints, like Find Users
- API calls using these credentials return empty responses, despite correct permissions and adherence to the scope limit.
- The current documentation and implementation do not provide sufficient clarity if that's supported.
Impact
- Users are unable to fully utilize service accounts for some workflows.
- Integration with external systems is hindered, affecting productivity and user experience.
Requested Solution
- Review and expand the available API scopes for service accounts.
- Provide clearer documentation on required scopes for all endpoints, including edge cases.
- Consider increasing the scope limit or allowing more granular scope assignment.
- Ensure that service accounts can access all necessary endpoints as documented.
- is duplicated by
-
CLOUD-12617 Add support for atlassian.net when sending web requests with scoped API tokens to avoid permission errors
- Gathering Interest