Atlassian Node.js add-on struggles with JWT auth. Sample code:
server.get('/ticket', verifyToken(), (req, res) => res.send('ok'));
Config snippet:
{"id": "addon-sample", "auth": "jwt"}
Based on my experience, the issues with JWT authentication sometimes trace back to configuration mismatches rather than code structure. I remember spending hours debugging because the middleware settings weren’t aligning with the expected JWT format. What eventually worked was setting up extensive logging to validate the token payload and ensuring the token signing key was accurately synchronized between our environment and the add-on configuration. A thorough review of the clock setup on your development machine can also be crucial, as discrepancies in system time may lead to token validation issues.