Jira shows Forbidden (403) error when setting up when using DC Helm charts on Kubernetes
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When setting Jira up using DC Helm charts, we get the Forbidden (403) error.
Environment
Any Jira DC version in Kubernetes, using the Atlassian DC Helm Charts.
Diagnosis
There is no certificate set in the values.yaml file.
Cause
The Jira DC Helm Chart expects that a certificate will always be set. In the chart's code we can see that the security scheme set in Tomcat is always set to "https" and "secure".
Solution
Configure a certificate to the deployment. Here's an example: Create certificate issuer
Was this helpful?