> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/userguide/release-notes/canakkale-edition/canakkale-5.5.0/canakkale-5.5.1.md).

# Canakkale 5.5.1

📅 Release Date: April 27, 2026 - 📅 Next Release Date: To Be Announced

## Release Summary

Autom Mate Canakkale **5.5.1** introduces OAuth 2.0 Client Credentials support for the Jira Software connector.

This update enhances integration capabilities by enabling secure, system-to-system authentication with Jira Software Cloud APIs. It allows automations to interact with Jira without relying on user-based authentication, improving scalability and security for backend workflows.

This release focuses on connector-level improvements and does not introduce changes to Monitoring, UI structure, or system architecture.

***

## **Highlights of this Release**

### ✨ **New Features**

* Introduced OAuth 2.0 Client Credentials support for Jira Software connector

***

## **Detailed Version**

{% tabs %}
{% tab title="✨ New Features" %}

#### Jira Software OAuth 2.0 Client Credentials Support

• Jira Software connector now supports OAuth 2.0 Client Credentials Grant\
This enables backend automations to authenticate without user interaction

• A new authentication type is available in credential configuration\
Users can select OAuth 2.0 Client Credentials when creating Jira credentials

• Required fields for configuration:\
◦ Jira Software Cloud URL\
◦ Client ID\
◦ Client Secret\
◦ Scope (comma-separated)

• Access tokens are automatically generated during execution\
Authentication is handled internally without manual token management
{% endtab %}
{% endtabs %}

***

## User Notices & Guidance

This section highlights important behavioral changes and system-level updates introduced in Canakkale 5.5.1.

{% hint style="danger" %}

#### Warnings (Critical Behavior Changes)

* OAuth Client Credentials is designed for system-to-system usage\
  User-based flows (e.g. OAuth Authorization Code) are not covered
* Proper scope configuration is required for Jira API access\
  Missing scopes may cause authentication failures
* Jira Software library version 1.70+ is required\
  Older versions will not support this authentication method
  {% endhint %}

***

{% hint style="info" %}

#### Hints (Productivity Tips)

* Use OAuth credentials for automation-heavy workflows
* Reuse credentials across multiple flows to simplify management
* Validate scopes based on Jira API requirements before deployment
  {% endhint %}

***

{% hint style="success" %}

#### Best Practices (Recommended Usage)

* Prefer OAuth Client Credentials for backend integrations
* Avoid using user-based credentials for automated processes
* Regularly review credential usage and permissions
* Ensure minimal required scopes are configured for security
  {% endhint %}
