Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62666

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

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          lucasc Lucas Cimon added a comment -

          We have written a PR and are in the process of testing the code in our production environment:
          https://github.com/jenkinsci/blueocean-plugin/pull/2077

          Show
          lucasc Lucas Cimon added a comment - We have written a PR and are in the process of testing the code in our production environment: https://github.com/jenkinsci/blueocean-plugin/pull/2077
          Hide
          olamy Olivier Lamy added a comment -

          pr merged 

          thanks

          merci!

          Show
          olamy Olivier Lamy added a comment - pr merged  thanks merci!

            People

            • Assignee:
              olamy Olivier Lamy
              Reporter:
              lucasc Lucas Cimon
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: