NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #3505 most downloaded on Packagist
A really simple library to generate user authentication JSON Web Tokens.
Latest stable
5.0.0
Last release 5 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 6 months
Most releases are documented
notes for 27 of 34 stable releases
Nothing withdrawn
no release was ever pulled
10 years old
46 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
This release upgrades the ReallySimpleJWT library to work with PHP 8 and above. It also makes some significant design tweaks to the underlying codebas
This release upgrades the ReallySimpleJWT library to work with PHP 8 and above. It also makes some significant design tweaks to the underlying codebase which should empower further improvements and functionality. The core interfaces for the library remain unchanged which should minimise the impact of the release.
The main design changes are the removal of the Secret class and interface, secret validation is now handled in the relevant encoding class. Token structure validation is now enforced in the Jwt value object class and not the Validator class. The Validate class now depends on the Parsed class, not the Parse class. This simplifies the Parse class and means token claim data access is only in one place.
Additional Work:
To Do:
sed command implementation in the CI pipeline.user_id and sub claims.Notes:
This is the Release Candidate for version 5.0.0, only minor fixes will be made from this point until the release. The main change for this release is ensuring the documentation is correct both in the code comments and in the README.
Additional Work:
To Do:
sed command implementation in the CI pipeline.Your coding agent can read these notes before it upgrades. Set up the MCP server →
This is the first release for version 5.0 of ReallySimpleJWT and introduces a number of significant architectural changes. It is a Beta release rather than an Alpha as it should work without any significant issues.
Version 5.0 further simplifies the code design and architecture, this should result in a more flexible library. And it should enable the introduction of Public-Private Keys for signature and token security.
The release will also upgrade the library to support PHP 8.1 and drop support for PHP 7.4. This needs to be done to enable the use of all the new features in PHP 8.0.
Additional Work:
To Do:
This is the Release Candidate for version 5.0.0, only minor fixes will be made from this point until the release. The main change for this release is
This is the Release Candidate for version 5.0.0, only minor fixes will be made from this point until the release. The main change for this release is ensuring the documentation is correct both in the code comments and in the README.
Additional Work:
To Do:
sed command implementation in the CI pipeline.This is the first release for version 5.0 of ReallySimpleJWT and introduces a number of significant architectural changes. It is a Beta release rather
This is the first release for version 5.0 of ReallySimpleJWT and introduces a number of significant architectural changes. It is a Beta release rather than an Alpha as it should work without any significant issues.
Version 5.0 further simplifies the code design and architecture, this should result in a more flexible library. And it should enable the introduction of Public-Private Keys for signature and token security.
The release will also upgrade the library to support PHP 8.1 and drop support for PHP 7.4. This needs to be done to enable the use of all the new features in PHP 8.0.
Additional Work:
To Do:
This release fixes a bug with the way the package validates Not Before claims in tokens. The Not Before claim defines when a token is usable from, it
This release fixes a bug with the way the package validates Not Before claims in tokens. The Not Before claim defines when a token is usable from, it should have validated when the nbf claim matched the current time, but it didn't. This has been resolved.
See issue #69 for further details.
Additional Work:
This security patch adds a check to the Tokens::validate() method to ensure the algorithm provided is not set to none as this may result in token misu
This security patch adds a check to the Tokens::validate() method to ensure the algorithm provided is not set to none as this may result in token misuse.
Additional Work:
This release makes some documentation improvements to the README based on issue #63 to make validation method usage clearer in the Token class.
This release makes some documentation improvements to the README based on issue #63 to make validation method usage clearer in the Token class.
Additional Work:
Version 4.0.0 of ReallySimpleJWT is a significant release as it makes numerous interface changes to improve the composability of the package. It also
Version 4.0.0 of ReallySimpleJWT is a significant release as it makes numerous interface changes to improve the composability of the package. It also upgrades PHP support from version 7.2 and above to version 7.4 and above.
The core Token class interface mainly remains unaffected by this release, but a lot of what sits behind it has changed. The Token class is now just a static interface wrapper around the new Tokens class. This enables developers to instantiate and inject the core ReallySimpleJWT functionality if they chose too.
In addition, the validation functionality which existed in the Parse class has been abstracted away and now just exists in the Validate and Helper\Validator classes. Also a number of interfaces for encoding, decoding and validation have been created, this increases composability and allows developers to amend functionality to meet their needs.
Additional Work:
To Do:
This is the Release Candidate for version 4.0.0 of the Really Simple JWT package. No further interface or functional changes will be made before the 4.0.0 release, only bug fixes and documentation updates.
The release focuses on documentation improvements to the README and the code comments. As a result of this a number of functionality and interface improvements have been made to make the code cleaner and clearer.
Additional Work:
To Do:
This Beta release gets version 4.0.0 into a working state and completes the design changes. Primarily it fixes the unit tests, integration tests and benchmark tests so they now all work with the new interfaces.
Additional Work:
ToDo:
This is the Release Candidate for version 4.0.0 of the Really Simple JWT package. No further interface or functional changes will be made before the 4
This is the Release Candidate for version 4.0.0 of the Really Simple JWT package. No further interface or functional changes will be made before the 4.0.0 release, only bug fixes and documentation updates.
The release focuses on documentation improvements to the README and the code comments. As a result of this a number of functionality and interface improvements have been made to make the code cleaner and clearer.
Additional Work:
To Do:
This Beta release gets version 4.0.0 into a working state and completes the design changes. Primarily it fixes the unit tests, integration tests and b
This Beta release gets version 4.0.0 into a working state and completes the design changes. Primarily it fixes the unit tests, integration tests and benchmark tests so they now all work with the new interfaces.
Additional Work:
ToDo:
This is the first 'working' release of ReallySimpleJWT version 4.0.0. This release focuses on integrating the architectural changes made in the pre-al
This is the first 'working' release of ReallySimpleJWT version 4.0.0. This release focuses on integrating the architectural changes made in the pre-alpha with the interface layers so tokens can be generated and parsed.
Additional Work:
To Do:
This security patch adds a check to the Parse::validate() method to ensure the algorithm provided is not set to none as this may result in token misus
This security patch adds a check to the Parse::validate() method to ensure the algorithm provided is not set to none as this may result in token misuse.
Additional Work:
none has been removed as a default from the validate algorithm method. This is because it could lead to a security vulnerability in a small number of…
none has been removed as a default from the validate algorithm method. This is because it could lead to a security vulnerability in a small number of instances. This functionality will be improved in version 4.0.0.
The main purpose of this release is to provide a means to validate the algorithm, or alg claim, of the supplied token. As such a validateAlgorithm() m
The main purpose of this release is to provide a means to validate the algorithm, or alg claim, of the supplied token. As such a validateAlgorithm() method has been added to the Parse class to enable this functionality. This allows for better compliance with RFC 7519.
This release also moves the CI pipeline from Travis CI to GitHub Actions. This wasn't planned but Travis seems to be experiencing a lot of problems lately so the decision was taken to move over now.
Additional Work:
To Do:
This release patches an issue where the two audience validation checks both return the same exception code but different messages. The Audience claim
This release patches an issue where the two audience validation checks both return the same exception code but different messages. The Audience claim is not set. exception now returns the code 11 instead of 2. The README documentation has been updated to match and surface this change.
Very small change which removes some unnecessary code bloat from the ValidateException class. Also adds a small addition to the CI pipeline to validat
Very small change which removes some unnecessary code bloat from the ValidateException class. Also adds a small addition to the CI pipeline to validate the Composer config.
This patch release resolves a bug in the PHPUnit config. This did not effect how the library functions but did break the CI mutation tests.
This patch release resolves a bug in the PHPUnit config. This did not effect how the library functions but did break the CI mutation tests.
Also this version adds some documentation amendments to the README to reflect changes made to the JavaScript library rs-jwt.
This is a breaking release which makes changes to the way token encoding / decoding works. Specifically abstracting the signature secret validation in
This is a breaking release which makes changes to the way token encoding / decoding works. Specifically abstracting the signature secret validation into a separate class and interface. This is so it is easier to implement custom signature secret validation. The release also bumps the minimum supported version of PHP to 7.2.
The other functional improvement is to add validate audience functionality to the parse and validate classes.
Full list of changes:
Future planned improvements:
All the functional changes are now in place for the release of version 3.0.0.
All the functional changes are now in place for the release of version 3.0.0.
The release candidate adds a validate audience method to the parse class so the audience claim can be validated in the same way as the expiration claim, etc. Added associated tests and amended exception messages.
Documentation and code need final review before release, along with the completion of some integration testing.
This beta release updates PHP to version 7.2 as the minimum requirement because PHP 7.1 is no longer supported.
This beta release updates PHP to version 7.2 as the minimum requirement because PHP 7.1 is no longer supported.
Its main aim is to solve the secret validation issue #43 by splitting the general validation features from the secret validation and implements a secret interface. This means developers can implement their own secret validation for environments which don't impose strict validation.
This release makes two new endpoints available via the Parsed class, getExpiresIn() and getUsableIn(). They tell developers how long until their token
This release makes two new endpoints available via the Parsed class, getExpiresIn() and getUsableIn(). They tell developers how long until their token expires and how long until it can be used, dependent on expiration and not before configuration.
The release also makes the following changes and improvements:
This will be the last significant release before version three is released in 2020.
A number of fixes made to readme documentation where code examples had broken syntax.
A number of fixes made to readme documentation where code examples had broken syntax.
Also added more information on setup with Composer based on feedback from users.
This release updates the README documentation:
This release updates the README documentation:
It also adds PHPLoc to the Travis CI pipeline for information purposes.
An issue was discovered where certain failing scenarios would not be properly captured by token validation.
An issue was discovered where certain failing scenarios would not be properly captured by token validation.
Changes:
This patch release resolves the issue where the jsonDecode method in the JsonEncoder trait will attempt to return null if an empty string is passed to
This patch release resolves the issue where the jsonDecode method in the JsonEncoder trait will attempt to return null if an empty string is passed to it. It should return an empty array.
Other minor amends include a change to PHPUnit so tests are run in a random order, and some minor comment changes.
This patch release resolves a bug discovered in the ReallySimpleJWT\Token::validate method.
This patch release resolves a bug discovered in the ReallySimpleJWT\Token::validate method.
The method would not correctly validate the Not Before claim if the Expiration claim did not exist in the token payload. The issue has been resolved and an additional unit test added to cover this scenario.
This is the first release of version two of the ReallySimpleJWT Library and is a significant improvement over version one. It is more RFC 7519 complia
This is the first release of version two of the ReallySimpleJWT Library and is a significant improvement over version one. It is more RFC 7519 compliant and offers a much better interface to build, parse and validate JSON Web Tokens.
It is a breaking release in all senses, 80%-90% of the code has been re-written since the release of version 1.1.0. Developers already using this library will need to take care when upgrading to this version and read the Readme documentation carefully so their software continues to function.
The main changes between version one and version two are:
ReallySimpleJWT::Token have been amended and new ones added.ReallySimpleJWT\Build and ReallySimpleJWT\Parse.EncodeInterface now available.Carbon\Carbon has been removed as a dependency.Hopefully the final release candidate before January 16th, 2019 v2.0.0 launch date.
Hopefully the final release candidate before January 16th, 2019 v2.0.0 launch date.
After review a number of amends and improvements have been made:
Parsed::getAlgorithm() helper method has been added.Token::customPayload() method has been added.Token::validate() method has been improved.Only code and documentation tidy up will be added to the release now.
This is the release candidate for version two of the ReallySimpleJWT library. Developers will notice significant differences to version one, it is nea
This is the release candidate for version two of the ReallySimpleJWT library. Developers will notice significant differences to version one, it is nearly a complete rewrite. The core of the library now revolves around the ReallySimpleJWT\Build and ReallySimpleJWT\Parse classes.
The ReallySimpleJWT\Token static interface class remains, but with amendments to the method names, and some additional functionality.
Everything outlined as to do in the beta release has been complete. Only minor amends and bug fixes will be applied before version two is released.
The version two release date will be Wednesday January 16th, 2019.
This is the beta release for version 2.0.0 and the code is now in a working state. Users can test this code and expect it to work correctly.
This is the beta release for version 2.0.0 and the code is now in a working state. Users can test this code and expect it to work correctly.
Tasks to do before release candidate is ready:
This is the second alpha release for version 2.0.0 of the ReallySimpleJWT library.
This is the second alpha release for version 2.0.0 of the ReallySimpleJWT library.
All the new code works now with only new code, this is still not production ready code.
The main classes to use for testing purposes are:
ReallySimpleJWT\Build to create tokens.ReallySimpleJWT\Parse to validate and access token data.This is the first alpha release for version 2.0.0 of the ReallySimpleJWT library.
This is the first alpha release for version 2.0.0 of the ReallySimpleJWT library.
It is a scrappy release and should not be used in production at all. It mainly serves as a marker for the direction in which version two of this library is heading.
Version 2.0.0 will be a significant departure from version 1 but will hopefully be a far more robust, extendable and expressive library as a result. The core static Token interface will remain however, it is what happens behind the Token class that will change significantly.
One of the main aims of this version is to allow developers to define their own JWT encoding.
This release makes available an addHeader() method in the TokenBuilder class so that you can add additional or custom header claims to your JSON Web T
This release makes available an addHeader() method in the TokenBuilder class so that you can add additional or custom header claims to your JSON Web Tokens.
There are also minor amendments to the README documentation.
This is most likely the final version one release as version two is now entering alpha and will be released early in 2019.
Thank you to @joelcuevas, @pacharrin and @pixeline for their contributions to this release.
Users have continued to experience issues with the nesbot/carbon dependency in this library.
Users have continued to experience issues with the nesbot/carbon dependency in this library.
An update has been made to composer.json so that the implementation of carbon is more flexible. This should not effect the functioning of the library.
Hopefully this will now finally fix #17
Minor update to use the latest version of the Carbon date time library.
Minor update to use the latest version of the Carbon date time library.
Fixes #17
It raised the issue that the expiry claim did not comply with the JWT RFC. The library has been updated so it now outputs the expiry claim as a date t
This release fixes #13.
It raised the issue that the expiry claim did not comply with the JWT RFC. The library has been updated so it now outputs the expiry claim as a date time number rather than a date time string. You can still generate tokens based on a date time string and it will still validate tokens that use a date time string for the expiry claim.
Other additions include:
assertEquals() to assertSame() so unit tests are more robust.Added PHP Mess Detection / PHP MD to project and fixed minor related bugs.
Added PHP Mess Detection / PHP MD to project and fixed minor related bugs.
Added PHPStan to the library which is a static analysis tool. Also added it to the Travis CI process.
Added PHPStan to the library which is a static analysis tool. Also added it to the Travis CI process.
PHPStan highlighted a number of errors in the codebase that have now been fixed, including using Self:: when I should have been using self::, and not namespacing the tests properly.
These edits in no way effect how the library runs though, all tests continue to pass.
In addition fixed minor text issue in the ReadMe.
This release fixes the issue where you could not generate two or more tokens at the same time, or one after the other.
This release fixes the issue where you could not generate two or more tokens at the same time, or one after the other.
The fix resets the builder class to allow multiple tokens to be created. A future improvement may be to develop a proper builder pattern to solve this problem in a more elegant manner.
Adds a number of new endpoints to provide more functionality.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.