public class JwtTokenService
    {
        public string Secret { get; }

        public JwtTokenService(string secret)
        {
            Secret = secret;
        }
        
        public string Create()
        {
            var headers = new Dictionary<string, object> {
                { "typ", "JWT" },
                { "kid", "app_62b5e0ffca5a3800f0225c53" }
            };

            var payload = new Dictionary<string, object> {
                { "external_id", "12316542344" },
                { "email", "janes@soap.com" },
                { "exp", "12345678" },
                { "name", "Jane Soaps" },
                { "scope", "user" }
            };
            
            var alg = new HMACSHA256Algorithm();
            
            IJsonSerializer serializer = new JsonNetSerializer();
            IBase64UrlEncoder urlEncoder = new JwtBase64UrlEncoder();
            IJwtEncoder encoder = new JwtEncoder(alg, serializer, urlEncoder); 
            return encoder.Encode(headers, payload, Secret);
        }
    }

• ViJump Support

  • 2022년 12월 29일 22:58

  I am having the same issue.
  
  Any help?

• Dane Wheeler

  • 2023년 03월 24일 04:15

  Check that your token is not expired. The "exp" field is specified in seconds since the UNIX epoch, so a token with exp = 12345678 expired sometime around February 1971. In TypeScript with the jsonwebtoken library, you could do something like:

  import jwt, { SignOptions } from "jsonwebtoken";
  const header = {
    alg:"HS256",
    typ:"JWT", 
    kid:zenDeskKid,
  };
  
  const options: SignOptions = {
    header,
    expiresIn: 60 * 60 * 6, // <-- this will convert to UNIX epoch time
  };
  
  const payload = {
    scope:"user",
    name: ...,
    email: ... ,
    external_id: ...,
  };
  
  var token = jwt.sign(payload, zenDeskSecret, options);

• Manuel Moreira

  • 2023년 04월 18일 15:51

  Also having a similar issue but mine says "JWT is malformed". Checked the timestamp in mine because of the reply above, but it's correct, like the rest of the JWT seems to be. 

• Dane Wheeler

  • 2023년 04월 18일 16:24

  Manuel Moreira did you try parsing your JWT and confirming it is properly formed? Try copy/pasting your JWT into https://jwt.io to make sure it is valid.

• Manuel Moreira

  • 2023년 04월 18일 16:26

  Dane Wheeler I have and yes it is valid

• Dane Wheeler

  • 2023년 04월 18일 17:30

  Manuel Moreira this sounds like a different issue than an expired JWT. For reference, below is what a working JWT looks like for my app. Perhaps you can compare yours to it to confirm you have the right header, field names, and data types.

• Manuel Moreira

  • 2023년 04월 19일 11:50
  • 편집된 시간

  Dane Wheeler it looks just like mine, so I have no idea what it could be

• Anastasiia Kalugina

  • 2023년 04월 27일 08:27

  I have the same problem. All as in Zendesk docs and JSON Web Tokens - jwt.io shows that all is correct.

• Manuel Moreira

  • 2023년 04월 27일 09:11

  Anastasiia Kalugina check if you are sending the token with quotation marks.it should not be sent with quotes

• Anastasiia Kalugina

  • 2023년 04월 27일 15:25

  Hi Manuel Moreira,
  
  Thanks for you response.
  What do you mean "with quotes"?
  
  For example, in JavaScript I have:
  
  const token = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImFwcF82NDRhMjMwYWRhZDg4MjliMWM1NmQ0ZjgifQ.eyJleHRlcm5hbF9pZCI6MSwic2NvcGUiOiJ1c2VyIiwiaWF0IjoxNjgyNTg3NzA5fQ.ICzTP9maSQQVX0xjEPyzou8IjAzhkPIqDLdkgZ3Q98Q'
  
  And I use it as argument in window.zE('messenger', 'loginUser', function(callback) {
      callback(token);
  })
  
  
  

• Anastasiia Kalugina

  • 2023년 04월 29일 18:22

  Anyone experiencing a similar problem, please read this article Enabling authenticated visitors in Web Widget (Classic) – Zendesk help. I have found that the messaging widget has similar features. Expiration time of token must be within 7 minutes and you should rotate it before its expiration time.

댓글을 남기려면 로그인하세요.