• Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login
FusionAuth
  • Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login

JKU in JWT Header

Scheduled Pinned Locked Moved
Q&A
0
6
2.3k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    amar.sibia
    last edited by 14 Apr 2021, 14:40

    Hi,

    We have a 3rd party integration to whom we are sending our JWTs, they have prescribed they need the JKU populated in the JWT header for them to correctly verify the token. I seem to be struggling to find any documentation or mention of how or even if it is possible to configure the jku header in the JWT. Is there a way to get the jku header to be populated correctly?

    FusionAuth™ version 1.22.2

    1 Reply Last reply Reply Quote 0
    • D
      dtokarz1
      last edited by 15 Apr 2021, 13:29

      I'm sure the support guys will chime in shortly but you can modify the JWT information with lambdas. Here is the link...

      https://fusionauth.io/docs/v1/tech/lambdas/

      1 Reply Last reply Reply Quote 0
      • A
        amar.sibia
        last edited by 19 Apr 2021, 16:01

        We're already using that to populate claims details, but the documentation implies this is the JWT payload only and not the header

        1 Reply Last reply Reply Quote 0
        • D
          dan
          last edited by 20 Apr 2021, 01:13

          You cannot modify JWT headers with a lambda. I can update the documentation to make that clearer.

          Please fee free to file an issue with your use case: https://github.com/fusionauth/fusionauth-issues/issues

          Here's our general roadmap guidance: https://fusionauth.io/docs/v1/tech/core-concepts/roadmap/

          --
          FusionAuth - Auth for devs, built by devs.
          https://fusionauth.io

          1 Reply Last reply Reply Quote 0
          • D
            dan
            last edited by dan 20 Apr 2021, 12:57

            I suppose one other option would be for you to have FusionAuth generate the JWT, then proxy the JWT, get the contents, add the JKU header, and then re-sign it. A brief googling indicates Kong can do this, maybe? https://docs.konghq.com/hub/kong-inc/jwt-signer/

            I also updated the documentation to make current limitations clearer: https://github.com/FusionAuth/fusionauth-site/pull/575

            Hope this helps.

            --
            FusionAuth - Auth for devs, built by devs.
            https://fusionauth.io

            1 Reply Last reply Reply Quote 0
            • D
              dan
              last edited by 23 Apr 2021, 15:21

              Updated the JWT populate lambda doc to make it clear that headers aren't modifiable at the present time: https://fusionauth.io/docs/v1/tech/lambdas/jwt-populate/

              --
              FusionAuth - Auth for devs, built by devs.
              https://fusionauth.io

              1 Reply Last reply Reply Quote 0
              2 out of 6
              • First post
                2/6
                Last post