Skip to content

Draft: Add additional JWT audiences when validating the Jira JWT token

Anton Smith requested to merge feat/jira-app-additional-audience into master

What does this MR do and why?

  1. Adds a new JSONB column called jira_connect_settings to the application_settings table
  2. Adds a new setting called jira_connect_additional_audience_url and exposes this in the Admin area > Settings > GitLab for Jira app > Jira Connect Additional Audience URL field
  3. If the additional audience is set, append this to the aud array during validation

These changes are to address an error that can occur when the JWT audiences mismatch. See the issue description in #498587.

References

Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request reports

Loading