Ending automatic token renewal for Jira and Confluence Data Center
Issued on July 29, 2026
GitGuardian is removing the system that automatically renews Personal Access Tokens (PATs) for Jira Data Center and Confluence Data Center integrations. If your integration still relies on it, update its token from the GitGuardian dashboard with a long-lived PAT before the deadline below.
What's changing
Until now, GitGuardian renewed the PAT behind your Jira Data Center and Confluence Data Center integrations before it expired. We are retiring this renewal system. Going forward, your integration uses the PAT you provide, and your team manages its lifecycle: GitGuardian no longer renews or replaces it.
Who's affected
- SaaS: Jira Data Center and Confluence Data Center integrations (sources and Jira notifiers) installed before April 3, 2026.
- Self-hosted: all deployments using these integrations.
Integrations installed after April 3, 2026 on SaaS, or whose token was already updated through the update flow, are not affected.
What you need to do
Update the token on your existing integration. Do not reinstall the integration: updating the token in place keeps your configuration and monitored perimeter intact.
- Create a new PAT in Jira or Confluence, with a long expiry or no expiry date. For Jira Data Center and Confluence Data Center source integrations, the PAT must belong to an administrator. For the Jira Data Center notifier, any user with access to the target projects works.
- In the GitGuardian dashboard, open the integration's settings and update its token with the new PAT. GitGuardian validates the token and runs a health check, so an unhealthy integration recovers immediately.
- If you use both a source integration and a notifier, update the token on each of them separately.
Once updated, the integration permanently leaves the renewal system. Make sure your team rotates the PAT before it expires, or use a non-expiring one.
Timeline
- SaaS: update your tokens before August 31, 2026. After this date, automatic renewal is removed and integrations still relying on it stop working when their token expires.
- Self-hosted: update your tokens before upgrading to release 2026.9.0, which removes the renewal system.
Questions
Reach out to your Customer Success Manager or email us at support@gitguardian.com.
