Jira Spoke - 'Bad Token' ErrorIssue Jira Webhook callback url is not working.Updates in Jira are not reflected in the instance and in the system logs we see : SEVERE *** ERROR *** sn_jira_spoke (JiraWebhookAuthenticator): Bad token Testing the same callback URL in postman works with no issuesCauseThe root cause of this issue is that Jira is decoding the UTF-8 based webhook callback URL using a non UTF-8 decoder. This is the reason why the issue is not observed if we try using postman to hit our endpoint. Token as seen in the webhook callback url %EF%B7%9E%EF%B7%9F%EF%B7%92aeb53c8c1b3a81d4758ba75b234bcb86%EF%B7%AC%EF%B7%941%EF%B7%AC%EF%B7%ADLl2QTbjJmURFdMphJ1auIA%3D%3DklsSn4NDa4CQvBWDX1OqR92NDEWW%EF%B7%AE%EF%B7%AF UTF-8 URL Encoded value of the encrypted token aeb53c8c1b3a81d4758ba75b234bcb861Ll2QTbjJmURFdMphJ1auIA==klsSn4NDa4CQvBWDX1OqR92NDEWW Token we get in the query params from Jira after hitting the callback URL. ï·žï·Ÿï·'aeb53c8c1b3a81d4758ba75b234bcb86ï·¬ï·"1ï·¬ï·Ll2QTbjJmURFdMphJ1auIA==klsSn4NDa4CQvBWDX1OqR92NDEWW﷮﷯ As the token in the Query parameters we received from Jira does not match the expected token, the callback fails with the Bad Token Error.ResolutionThe issue was resolved by Jira support with a configuration change on the Jira server Edit conf/server.xml and find the line where the HTTP Connector is defined. It will look something like this, possibly with more parameters - <Connector port="8080"/> Add a URIEncoding="UTF-8"property to the connector: <Connector port="8080" URIEncoding="UTF-8"/> Restart Tomcat