Published Date: March 24th, 2026
Validated: Yes
Audience: Everyone, Jama Connect® Users, Internal
Products and Versions Covered:
- Jama Connect Interchange™
- JCI Module: Jira Cloud
Summary
Jama Connect Interchange does not support Jira Service Accounts. Standard Jira accounts are needed for creating connectors. Jira Service Accounts, cannot use un-scoped API tokens, which are currently required. Users will see an error message when creating a Connector with a scoped Service Account:
Please confirm Credentials are correct.
and an HTTP response 403:
Resolution
Please use standard Jira accounts which can be un-scoped.
Additional Resources
- Jira Service Accounts
- Allow Service Accounts to Create Non-Scoped API Tokens in Jira Cloud
- Success Programs
- Success Catalog
- Datasheets
-
Request a Solution Offering or Training from the Success Catalog
Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.
Comments
1 comment
Just found this article after struggling for some hours to make my connector work. It's a pity you don't yet support Atlassian service accounts. It would have saved me some time if the error message returned was a little more informative (there are many ways the credentials could be insufficient). This article was helpful, but a better solution would be to provide a clear explanation of root cause in the error message.
Please sign in to leave a comment.