Using Service Accounts for REST API Integrations in Jama Connect®

Sravya Bandari
Sravya Bandari
  • Updated

Audience: Everyone

Products and Versions Covered: 

  • Cloud/CVC
  • Self-hosted, Replicated - KOTS
  • Jama Connect®

IMPORTANT: Access to the REST API is limited to users with a Named Creator Jama Connect license, including endpoints in v1, labs, and SCIM. Users without a Named Creator Jama Connect license, including those with a Creator Float License, do not have access.

Summary

Service accounts enable API integrations to function independently of individual user credentials. Actions performed via the API are attributed to a technical user (e.g., "API Service") rather than to a personal account.

Resolution

  1. Create a dedicated service account in Jama Connect with a Creator license.
  2. Generate API credentials (client ID and client secret) for this account.
  3. Utilize these credentials in your REST API requests to authenticate as the service account.

Key Benefits

  • Change logs display "API Service changed the status" instead of attributing actions to a specific user.
  • Supports up to 20 API credential pairs (client ID and client secret) per service account, allowing integration with multiple tools.
  • Eliminates reliance on individual user licenses for routine API operations.

Additional Resources 

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

 

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.