Using OSLC services

Open Services for Lifecycle Collaboration (OSLC) is a community that is standardizing the way that lifecycle tools work together. OSLC Connect for Jira supports the OSLC data sharing specification as a provider for the Change Management (CM) domain and as a consumer of other domains.

The sharing of OSLC data between domains is based on a common set of resources, formats, and REST architectural services.

The data sharing supports these transactions:

• Linking that is based on HTTP protocol
• Identification of resources by URIs
• Information retrieval that uses industry standard media types

Please refer to this site to get more information on OSLC: https://open-services.net/

Authentication

OSLC Connect for Jira supports BASIC authentication, so that you can easily execute REST services using the Jira user and password of your choice in the Authorization request header.

The Authorization request header must be BASIC value, where value is jira-user:jira-password Base64 encoded. Refer to https://en.wikipedia.org/wiki/Basic_access_authentication for details.

HTTP Status

Each HTTP response has an associated HTTP status that can either be:

• HTTP 200: the request was successfully executed.
• HTTP 400: the request is invalid, the response body should contain information on the root cause.
• HTTP 401: the authentication failed, probably because the user name and password do not match an existing user in Jira.
• HTTP 403: the authentication succeeded but you don't have permission to read or update the Jira issue
• HTTP 404: the resource is not found, which may mean the identifier does not resolve an existing Jira issue (e.g. it has been deleted).
• HTTP 500: an error occurred on server side, contact your Jira administrator to check Jira's log files to identify the root cause.