Releases: azutoolkit/authly
Releases · azutoolkit/authly
Release v1.2.7
Fix require
Release v1.2.6
Merge remote-tracking branch 'refs/remotes/origin/master'
Release v1.2.5
Update CI badge URL in README Revised the Crystal CI badge URL to reflect changes in the repository's GitHub actions workflow path, ensuring the badge displays the correct build status. This helps maintain accurate CI status visibility and project credibility.
Release v1.2.4
Improve test file pattern for Grants in CI workflow Updated the pattern for running Grants tests in the CI workflow to target only files with a '_spec.cr' suffix, ensuring that only spec files are executed and reducing the chance of unnecessary or incorrect file execution. This change streamlines the test process and aligns with existing practices for other test sets.
Release v1.2.3
Code formatting
Release v1.2.2
Refine revoked getter and improve enumeration Changed the `revoked` getter to a nilable type for consistent handling of null values in JSON serialization, avoiding potential bugs. Improved the `each` method in the in-memory JTI provider by utilizing block notation, simplifying code readability and maintainability. These enhancements streamline data handling and iteration in the codebase.
Release v1.2.1
Enhance token introspection with detailed validation Added and refined tests for the introspection method to cover scenarios for active and inactive tokens, improving test coverage and reliability. Updated the introspection logic to ensure more precise extraction and validation of token information, addressing potential issues with JWT decoding and token expiration handling. The changes offer a more robust introspection process by aligning token payload parsing with expected structures.
Release v1.2.0
(MINOR) allows passwing jwt algorithm
v1.1.1: Cleans up scope variable
Scope variable is only needed for Authorization Code Flow Note: In the case of no scope present we can default to client default scopes.