Skip to content

2.9.x Jira

2.9.0

Security Fixes & New Feature

  • Fixed several security issues. Please read this advisory for more details: 2026-11-18 - Security Bulletin for API Token Authentication 2.9.0

  • New: header/ value access rules can be switched off or limited to groups; please read the Admin Guide for details

    • After the update, the feature stays switched on for everyone who can create tokens

  • Behavior changes:

    • Read-only tokens can no longer be used to create, rename, or delete tokens through the REST API

    • Invalid values are refused with a 400 error when a token is created through the REST API, and requests without a tokenScope are deprecated

    • If you use IP restrictions behind a reverse proxy, check the reverse proxy settings before the update, because requests with API tokens can be refused afterward

      • Every proxy between the client and Jira must be listed as a trusted reverse proxy

      • The list of trusted reverse proxies must contain proxies only, no addresses or ranges of clients

    • New or changed header/ value access rules are checked when they are saved; very complex regular expressions are refused

  • Fixed an issue that caused requests to eazyBI with our tokens to fail

  • Updated 3rd-party and internal libraries