Jama Software · Authentication Profile

Jama Software Authentication

Authentication

Jama Software secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyRequirements ManagementApplication Lifecycle ManagementTraceabilityTest ManagementProduct DevelopmentSystems EngineeringREST API
Methods: http, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in:

Security Schemes

basicAuth http
scheme: basic
oauth2ClientCredentials oauth2

Source

Authentication Profile

jama-software-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://dev.jamasoftware.com/api/
docs: https://dev.jamasoftware.com/api/
summary:
  types: [http, oauth2]
  http_schemes: [basic]
  oauth2_flows: [clientCredentials]
schemes:
  - name: basicAuth
    type: http
    scheme: basic
    description: >-
      HTTP Basic authentication (RFC 2617) using a Jama Connect username and
      password in the Authorization header. Available on all Jama Connect
      deployments.
    sources: [https://dev.jamasoftware.com/api/]
  - name: oauth2ClientCredentials
    type: oauth2
    flow: clientCredentials
    tokenUrl: /rest/oauth/token
    description: >-
      OAuth 2.0 client-credentials grant. Available on Jamacloud and self-hosted
      8.62+. POST to /rest/oauth/token with grant_type=client_credentials using
      the client ID as HTTP Basic username and the client secret as password;
      the response returns an access_token and expires_in (default 3600s). Send
      the token as Authorization: Bearer {access_token} on subsequent calls.
    sources: [https://dev.jamasoftware.com/api/]
notes:
  - OAuth clients are provisioned by each user under their Jama Connect profile (API credentials).
  - As of Jama Connect 9.4 the REST API is restricted to Creator-license users.