Action Required - Atlassian Connect installation lifecycle security improvements

Announcements
, , , ,
61

UPDATE 2: I deployed to production and ran into this again, so I reverted back to using jwt.SymmetricAlgorithm.HS256 again to fix the issue.

UPDATE: Don’t know why, but this is working now.

@HanjooSong can you please check out this related issue with atlassian-jwt discussed in this thread:

Atlassian-jwt 2.0 Algorithm from the header “HS256” does not match - Jira Development / Jira Cloud - The Atlassian Developer Community

This caused a lot of wasted time, but subject to testing, I think I resolved it.

I had to use decoded = jwt.decodeSymmetric(token, secret, jwt.SymmetricAlgorithm.HS256); yet decoded = jwt.decodeAsymmetric(token, response, ‘RS256’); works.