Releases: nats-io/jwt
Releases · nats-io/jwt
Release v2.0.2
Changelog
Fixed
- Regular expression to accept EOF/newline at the end of the decoration (#151)
Complete Changes
Release v2.0.1
Changelog
Fixed
- Import validation to return error when token are in the wrong context (#149)
Complete Changes
Release v2.0.0
Changelog
Added
- Information link and description to account and export (#122)
- Ability to specify headers for latency tracking (#125)
- Ability to have wildcards export/imports (#131)
- Roles for signing keys (#129)
- Generic claims can now have custom types (#132)
Keys()
function toSigningKeys
which returns all signing keys in the account (#134)- New field
LocalSubject
to rename the remote subject (#137) - Accessor to read
To
without deprecation warning (#138) - Flag enforcing subordinate objects to be signed with signing keys (#140)
- Advertise flag to exports and extending maximum description length (#143)
- Support for account mappings (#145)
Deprecated
- The
To
subject in imports (#137)
Removed
- JWT activation token as URL and corresponding download (#144)
Fixed
- Import token validation (#124)
- Removed unnecessary warning for imports without token (#130)
- Ensure that generic claims type is a string (#133)
- Missing validation for permissions (#139)
- Fixed default value for JetStream to be 0 (disabled) (#141)
op.DidSign(op)
when strict signing key usage was enforced (#142)
Updated
- Dependencies to nkeys v0.3.0 (#147)
Complete Changes
Release v1.2.2
Release v1.2.0
Changelog
Added
- Allow revocations to have a pub key of '*' which matches any JWT issued. This enables mass revocations based on a single time without the need to know the public key (#114)
Complete Changes
Release v1.1.0
Release v1.0.1
Release v0.3.2
v0.3.0
v0.2.16
This release adds the ability to track service latency for exported services.