> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.226/help-center-index/faqs/jira-faqs/types-of-authentication-jira.md).

# Which authentication modes for Jira On-Premise instance are supported for synchronization?

### Description

Which authentication modes for Jira On-Premise instance are supported for synchronization?

### Solution

There are two types of authentication modes that are supported for Jira On-Premise instance. In both of these authentication modes username and password of the user will be used but <code class="expression">space.vars.OIM</code> will internally handle how it will make authenticated REST API request with the server.

These are the two authentication modes:

1. **Basic Authentication**: If this mode is selected, then Jira will internally log-in for every API call sent during integration.
2. **Cookie-based Authentication**: If this mode is selected, then one-time cookie session will be generated that will be used for all subsequent API requests sent during integration.

It is recommended to use Jira Cookie-based Authentication over Basic Authentication as there would be significant improvement in <code class="expression">space.vars.OIM</code>'s performance as Jira will not login for every API call sent during integration.

<code class="expression">space.vars.OIM</code> **support for Cookie-based Authentication:**\
The Cookie-based Authentication for Jira system has been incorporated from <code class="expression">space.vars.OIM</code> Version 6.9 U1.

**How to Configure**\
Configure Authentication Type in system configuration of Jira. For more details on Jira's system configuration refer: [System Configuration of Jira](/v7.226/connectors/jira.md#system-configuration)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opshub.com/v7.226/help-center-index/faqs/jira-faqs/types-of-authentication-jira.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.