JWT v1.5.5 Release Notes
Release Date: 2016-09-16 // over 7 years ago-
๐ Full Changelog
Implemented enhancements:
- ๐ JWT.decode always raises JWT::ExpiredSignature for tokens created with Time objects passed as the
exp
parameter #148
๐ Fixed bugs:
- ๐ expiration check does not give "Signature has expired" error for the exact time of expiration #157
- ๐ JTI claim broken? #152
- ๐ Audience Claim broken? #151
- ๐ 1.5.3 breaks compatibility with 1.5.2 #133
- ๐ Version 1.5.3 breaks 1.9.3 compatibility, but not documented as such #132
- ๐ Fix: exp claim check #161 (excpt)
Closed issues:
- ๐ Rendering Json Results in JWT::DecodeError #162
- ๐ PHP Libraries #154
- ๐ [security] Signature verified after expiration/sub/iss checks #153
- ๐ Is ruby-jwt thread-safe? #150
- ๐ JWT 1.5.3 #143
- ๐ gem install v 1.5.3 returns error #141
- โ Adding a CHANGELOG #140
๐ Merged pull requests:
- โฌ๏ธ Bump version #165 (excpt)
- ๐ Improve error message for exp claim in payload #164 (excpt)
- ๐ Fix #151 and code refactoring #163 (excpt)
- ๐ Signature validation before claim verification #160 (excpt)
- ๐ Create specs for README.md examples #159 (excpt)
- ๐ Tiny Readme Improvement #156 (b264)
- โ Added test execution to Rakefile #147 (jabbrwcky)
- โ Add more bling bling to the site #146 (excpt)
- โฌ๏ธ Bump version #145 (excpt)
- โ Add first content and basic layout #144 (excpt)
- โ Add a changelog file #142 (excpt)
- ๐ Return decoded_segments #139 (akostrikov)
- ๐ JWT.decode always raises JWT::ExpiredSignature for tokens created with Time objects passed as the