Fix documentation error

Changed documentation as the expiry date is for the refresh token instead of the access token
This commit is contained in:
Andrew Millington 2018-12-06 23:25:50 +00:00 committed by GitHub
parent 6235cb2cb8
commit f42c821a18
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -20,7 +20,7 @@ When a new refresh token is created this method will be called. You don't have t
The refresh token entity passed in has a number of methods you can call which contain data worth saving to a database: The refresh token entity passed in has a number of methods you can call which contain data worth saving to a database:
* `getIdentifier() : string` this is randomly generated unique identifier (of 80+ characters in length) for the refresh token. * `getIdentifier() : string` this is randomly generated unique identifier (of 80+ characters in length) for the refresh token.
* `getExpiryDateTime() : \DateTime` the expiry date and time of the access token. * `getExpiryDateTime() : \DateTime` the expiry date and time of the refresh token.
* `getAccessToken()->getIdentifier() : string` the linked access token's identifier. * `getAccessToken()->getIdentifier() : string` the linked access token's identifier.
JWT access tokens contain an expiry date and so will be rejected automatically when used. You can safely clean up expired access tokens from your database. JWT access tokens contain an expiry date and so will be rejected automatically when used. You can safely clean up expired access tokens from your database.