Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-3167

InvalidKeyException: Key is null in JWT response

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • 1.9.4.Final
    • 2.1.0.CR1
    • OIDC
    • None

    Description

      I am configuring Keycloak as openID connect provider and IBM Websphere Application Server as Relying Party.

      But when the token is issued by keycloak the RP could not verify the token because the key is null. below is the JWT (which I had taken from Websphere logs during authentication)

      --------------------------
      JWT(tokenString[eyJhbGciOiJSUzI1NiJ9.eyJqdGkiOiIwNGE0MDYyNy0yMWQ1LTQwOTYtYjMyZC03OTYxZjk4ZDMzMjgiLCJleHAiOjE0NjY2NzQwODgsIm5iZiI6MCwiaWF0IjoxNDY2NjczNzg4LCJpc3MiOiJodHRwczovLzEwLjYzLjE0LjMzOjg0NDMvYXV0aC9yZWFsbXMvRGVtbyIsImF1ZCI6Im5ldGFjdCIsInN1YiI6IjBkNDQwZWZkLTc4OGItNDY4NS1hNDZiLTFjYzBjZmQwYjA4YyIsInR5cCI6IklEIiwiYXpwIjoibmV0YWN0Iiwic2Vzc2lvbl9zdGF0ZSI6ImQ3NGQ2OWZjLTBmNTEtNGI5My04MGUzLTQyODFmMDM2N2EwYSIsIm5hbWUiOiJvbWMgb21jIiwicHJlZmVycmVkX3VzZXJuYW1lIjoib21jIiwiZ2l2ZW5fbmFtZSI6Im9tYyIsImZhbWlseV9uYW1lIjoib21jIn0.NQM4eZVK0hD5iyBakeW8Sfk8vY4uOJDIl-8k9CXlCWnZsE1tsgaPX5TCmLnJH6QOgfgXnIlIPROqpEw_Hxg9IWF_7AvayE1kp-2xIn7exZcvQgKKqcYKEpsLJftngh-UuI9KGwdO_CeA8AWolYMPob_bEyULxQlyBB5kkAys8HykDApL5yXdjnQp0qRTwoT5fS8OZxrzxdrkcBbAkKWbT-tDBIe3muu7x4QSUuJ7fLjptagTAEWtTLXUyG9XSU80PZr9p4xLIPJcACgBJ1Bd7M4MRSHe0AOVke1kfQffmh2B4kWiebsMJBwSKawoaY2YtJN4tyiaWYZFvqu4bGU65Q], key[null],clientId[netact],issuerhttps://10.63.14.33:8443/auth/realms/Demo,signingAlgorithm[RS256])
      ----------------------

      I have attached the stack trace for the issue also. Could someone explain why the token verification is failing?

      How to resolve this issue?

      Thanks in advance

      Attachments

        Issue Links

          Activity

            People

              sthorger@redhat.com Stian Thorgersen
              susthan_jira Suseendhiran Thangarasu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: