> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parable.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Personal Access Token

> Connect Parable to Jira Server using a Personal Access Token

export const platform_1 = "Jira Server"

export const limit_0 = "varies by server configuration"

export const platform_0 = "Jira Server"

export const role_0 = undefined

export const tokenName_0 = "personal access token"

<Tabs>
  <Tab title="Setup">
    <Card title="What You'll Need" icon="key">
      | Credential                | What it is                  |
      | ------------------------- | --------------------------- |
      | **Username**              | Jira account username       |
      | **Personal Access Token** | Generated from Jira profile |
      | **Base URL**              | Your Jira Server URL        |
    </Card>

    ## Overview

    Connect Parable to Jira Server or Data Center using Personal Access Tokens (PATs) for secure API access without exposing passwords.

    ## Prerequisites

    <Info>
      **Setup access in {platform_0}.** These steps require **{role_0}**, or a colleague with equivalent permissions who can create credentials for you.

      If that is not you, ask your {platform_0} administrator.
    </Info>

    * **Jira Administrator** or user with Browse Projects permission
    * Personal Access Tokens enabled on your instance (Jira 8.14+)
    * Network access to your Jira Server

    ## Setup Guide

    <Steps>
      <Step title="Access Profile Settings">
        1. Log in to your Jira Server instance
        2. Click your avatar → **Profile**
        3. Navigate to **Personal Access Tokens**

        <Info>
          PATs require Jira Server 8.14 or later. For older versions, use Basic Auth with username/password.
        </Info>
      </Step>

      <Step title="Create Personal Access Token">
        1. Click **Create token**
        2. Enter name: `Parable Integration`
        3. Set expiration (optional)
        4. Click **Create**

        <Warning>
          **Copy your {tokenName_0} now!**

          This is the only time it will be displayed. Store it in a secure password manager before closing this page.
        </Warning>
      </Step>

      <Step title="Note Your Base URL">
        Your Jira Server URL format:

        ```
        https://jira.yourcompany.com
        ```
      </Step>

      <Step title="Enter values in the form">
        1. Enter **Username**, **Personal Access Token**, and **Base URL** in the connector form.
        2. Click **Save & test connection**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Reference">
    ## Verify Your Setup

    <CodeGroup>
      ```bash With Personal Access Token theme={null}
      curl -H "Authorization: Bearer YOUR_TOKEN" \
        "https://jira.yourcompany.com/rest/api/2/myself"
      ```

      ```bash With Basic Auth (older versions) theme={null}
      curl -u "username:password" \
        "https://jira.yourcompany.com/rest/api/2/myself"
      ```
    </CodeGroup>

    <Check>
      **Success!** If you received a `200 OK` response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.
    </Check>

    ## API Differences from Cloud

    | Feature     | Jira Server  | Jira Cloud        |
    | ----------- | ------------ | ----------------- |
    | API Version | v2           | v2 and v3         |
    | Auth        | PAT or Basic | API Token + Basic |
    | Base URL    | Custom       | `*.atlassian.net` |
    | Audit Logs  | Limited      | Full              |

    <Tip>
      **Rate Limits:** {platform_1} enforces rate limits of **{limit_0}**.

      Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
    </Tip>

    ## Troubleshooting

    | Error                | Meaning             | Solution                             |
    | -------------------- | ------------------- | ------------------------------------ |
    | `401 Unauthorized`   | Invalid credentials | Verify username and token/password   |
    | `403 Forbidden`      | No permission       | Check user has required permissions  |
    | `Connection refused` | Network issue       | Verify server URL and network access |

    <Accordion title="Common Issues">
      ### PATs not available

      Personal Access Tokens require Jira 8.14+. For older versions, use Basic Authentication.

      ### SSL certificate errors

      Self-signed certificates may cause issues. Ensure proper certificate configuration.
    </Accordion>

    ## Additional Resources

    <CardGroup cols={2}>
      <Card title="Jira Server REST API" icon="book" href="https://docs.atlassian.com/software/jira/docs/api/REST/latest/">
        Official API documentation
      </Card>
    </CardGroup>
  </Tab>
</Tabs>