Related tickets:
- Issue #45: High number of 500 errors registered in the logs -when attempting to read/validate the token
Related tickets:
Related tickets:
Related tickets:
Related tickets:
Related tickets:
Related tickets:
Related tickets:
Related tickets:
Fixed lost access to WebSudo secured endpoints.
Related tickets:
Fixed lost access to WebSudo secured endpoints.
Related tickets:
Now API Tokens for Jira plugin also cover 'plugins/servlet/*' URLs (as well as 'rest/*').
Added compatibility with "Power BI Connector for Jira" plugin.
Fixed:
Now API Tokens for Jira plugin also cover 'plugins/servlet/*' URLs (as well as 'rest/*').
Added compatibility with "Power BI Connector for Jira" plugin.
Fixed:
Implemented:
Implemented:
Now users got an ability to select for how long the token is needed.
All tokens will expire automatically.
Now users got an ability to select for how long the token is needed.
All tokens will expire automatically.
Fixed:
Fixed:
Minor fixes and implemented:
Minor fixes and implemented:
Features:
Features:
Issue reproduced only on v1.1.6 and Postgres DB
Fixed:
Issue reproduced only on v1.1.6 and Postgres DB
Fixed:
Fixed
Fixed
Fixed
Fixed
Added support for cookie-based authentication
Improved authentication process
Fixed
Added support for cookie-based authentication
Improved authentication process
Fixed
Tuned deploy processes and logging
Tuned deploy processes and logging
Fixed:
Fixed:
API Tokens for Jira align with all strict requirements for highly loaded cluster Jira installations!
API Tokens for Jira align with all strict requirements for highly loaded cluster Jira installations!
Fixed:
Extended support to Jira 7.0.0
Added link to the documentation
From now any API calls (even to 3rd REST endpoints) will be covered by tokens check