Releases: API-Skeletons/zf-oauth2-doctrine
1.0.0
Support for multiple OAuth2 servers through zfcampus/zf-mvc-auth. Configuration has changed significantly from the 0.3 series.
0.3.5
THIS IS THE FINAL RELASE OF THE 0.3 SERIES. FUTURE RELEASES WILL BE TAGGED 1.* AND WILL BE SIGNIFICANTLY DIFFERENT IN THEIR FORM but they will still accomplish the same goal.
No significant features are new in this final 0.3 release.
0.3.4
OAuth2Server Initializer. This injects the OAuth2 server into Query Providers and Query Create Filters.
0.3.3
Removed console routes.
0.3.2
A null user is allowed for every user reference. This change still allows users to be set but will not require them through the ORM.
Console routes have been removed and will be moved to a new repository: https://github.com/StukiOrg/zf-oauth2-doctrine-console
0.3.1
0.3.0
This release address cryptography in OAuth2.
Two schema changes are made.
- AccessToken.accessToken is now a text field to support use_jwt_access_tokens
- Client to PublicKey is now a 1:1 relationship
Two new console routes are available to populate the PublicKey table and create a new Jwt entry.
0.2.4
Corrections to JTI / JWT
0.2.3
Deletes are now cascaded by default.
A correction to JTI expires field (was expiration in the mapper). This does not require a database change.
If upgrading you will need to make a change to your local config:
At TomHAnderson@0192552#diff-7b846b2764d600cb9afb837978a52025L257 in the JTI config change 'expiration' to 'expires'.
0.2.2
Additional mapping data for identifiers which do not conform to the Doctrine naming strategy.
Multiple user identifiers may be used for authentication.