entvex opened a new issue, #22811: URL: https://github.com/apache/pulsar/issues/22811
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### Version The versions affected 3.2.0 3.2.1 3.2.2 and 3.2.3 ### Minimal reproduce step Create a JWT token using an affected version. bin/pulsar tokens create --secret-key /pulsar/secret.key --subject test-user --expiry-time 3600s Use a [JWT decoder](https://jwt.io/) and you will see that the expiry time is wrong. ### What did you expect to see? A JWT token with the desired --expiry-time ### What did you see instead? As a workaround, you can multiply the --expiry-time by 1000 ### Anything else? It appears that the bug was introduced in this pull request: [GitHub link](https://github.com/apache/pulsar/pull/21412/files). I'll work on fixing it and submit a pull request. Additionally, I'll look into adding test coverage. ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
