JWKS: adding an endpoint to get a JSON output that follows RFC 7517

This issue is archived. You can view it, but you can't modify it. Learn more

      Currently the blueocean-jwt plugin provides an endpoint allowing to retrieve a JWK based on its keyID: https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-jwt#json-web-key-jwk-api

      However, most tool (and in our case: HashiCorp Vault) expect a public endpoint that follows the format of the RFC 7517 spec, with a top-level "keys" field: https://tools.ietf.org/html/rfc7517#page-10

      We propose to add a new /jwt-auth/jwks endpoint that would provide exactly that.

            Assignee:
            Olivier Lamy
            Reporter:
            Lucas Cimon
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: