Skip to content

Include JWT signing key in application secrets in docs

Tim Poffenbarger requested to merge poffey21-master-patch-20050 into master

What does this MR do and why?

Describe in detail what your merge request does and why.

This aims to mention that as of 13.6, the JWT has a dedicated signing key for all installations.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

Current state: https://docs.gitlab.com/ee/development/application_secrets.html#secret-entries

Screen_Shot_2022-07-20_at_8.51.54_AM

Also... this still needs worked on. #221031 (closed)

How to set up and validate locally

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

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Tim Poffenbarger

Merge request reports