0.5.2

• fixing token refreshing
• adding JWTFactory facade

0.5.1 Security Release

• bumping version of namshi/jose to address this issue
• making config instances more configurable
• fixing token refreshing, as described in #63

0.4.2 Security Release

• bumping version of namshi/jose to address this issue

0.4.1

• fallback to no tags on cach provider (when using file or db drivers)

0.5 Release

This release targets Laravel 5

• switching to psr-4
• switching to phpunit & Mockery
• switching to namshi/jose as it provides gretaer control over token verification
• using carbon for date/time calculations
• abstracting the providers - (Auth, User, Storage, JWT)
• adding lots more test coverage
• completely refactoring Claim validation and Payload building
• adding support for refreshing tokens
• adding support for blacklisting tokens
• login() renamed to authenticate()
• lots of other general improvements and refactors

0.4 Release

This release targets Laravel 4

• switching to psr-4
• switching to phpunit & Mockery
• switching to namshi/jose as it provides gretaer control over token verification
• using carbon for date/time calculations
• abstracting the providers - (Auth, User, Storage, JWT)
• adding lots more test coverage
• completely refactoring Claim validation and Payload building
• adding support for refreshing tokens
• adding support for blacklisting tokens
• login() renamed to authenticate()
• lots of other general improvements and refactors

0.3.12

• fixing double quotes message on exception
• fixing issue where boolean is returned from login method instead of authenticated user

0.3.11

• another hotfix :/

0.3.10

• hotfix release

0.3.9

• fixing issue with firebase provider throwing exception when token has expired - see #14