JIRA DVCS integration failing to renew token every two hours, unable to authenticate
In #340848 (closed), we enforced OAuth token expiry as a breaking change for 15.0.
This has exposed an issue with the Jira DVCS integration, as reported in several tickets including:
- https://gitlab.zendesk.com/agent/tickets/298682 (internal link)
- https://gitlab.zendesk.com/agent/tickets/298028 (internal link)
- https://gitlab.zendesk.com/agent/tickets/305689 (internal link)
A temporary workaround for self-managed customers has been suggested that involves modifying
/opt/gitlab/embedded/service/gitlab-rails/config/initializers/doorkeeper.rb and specifying
access_token_expires_in 1.week (or
1.year etc.) to change the token expiry from 2 hours, but there is no workaround for SaaS customers. e.g.
# frozen_string_literal: true Doorkeeper.configure do access_token_expires_in 1.week # Change the ORM that doorkeeper will use.
Atlassian have opened a Sev 2 bug ticket at https://jira.atlassian.com/browse/JSWSERVER-21389 with a fix due to be released in Jira versions 9.1.0 and 8.20.11, tentatively scheduled for release on 2022-07-19. GitLab SaaS customers using the Jira DVCS integration should upgrade when the new versions are available.