Closed yhuang8 closed 10 years ago
Sorry for the late reply on this - been really busy. I'll check this out shortly - I agree with the base64 piece but I want to validate the second piece as I did do fairly thorough evaluation of the output against the spec.
BTW thank you so much!
No problem. not in a hurry. =)
Thanks so much!
Hey this broke the tests for me so I reverted for now. I'll revisit later. Did you run the unit tests before creating a pr?
sorry about that. I tested the one for my company but totally forgot running unit tests here. Will send out a new pr again. Thanks a lot!
No worries - would correct the tests but I'm hammered with competing tasks atm - really appreciate it.
Sent from my iPhone
On Sep 13, 2014, at 6:59 PM, Yan Huang notifications@github.com wrote:
sorry about that. I tested the one for my company but totally forgot running unit tests here. Will send out a new pr again. Thanks a lot!
— Reply to this email directly or view it on GitHub.
when the string is too long, current version of base64 will add newline to the string which is not url safe.
secondly, according to this https://developer.atlassian.com/static/connect/docs/concepts/understanding-jwt.html the last encoded signature is wrong.