Token Storage
You can enable token storage in cbsecurity via the tokenStorage
setting. By default it is enabled and leverages CacheBox's default
cache using a key prefix of cbjwt_
+ the token's unique identifier claim of jti
.
We recommend that you create a separate provider for the cache.
Why use a storage?
The storage of keys are great in order to visualize in your application all the registered keys in the system. You can also invalidate keys, as by default if the token does not exist in the storage, it is considered invalid.
You can retrieve the token storage by injection or the helper method:
Storage Drivers
We ship with two drivers:
cachebox
: Leverages any cache registered in CacheBoxdb
: Leverages a database table to store the keys
CacheBox Driver Properties
cacheName
: The cache to use
DB Driver Properties
table
: The table to use for storageschema
: A schema to use if the database supports it, else emptydns
: The datasource to use, defaults to the one set inApplication.cfc
autoCreate:true
: Autocreate the table if not foundrotationDays:7
: How many days should the expiration be before removalrotationFrequency:60
: How many minutes should pass before issuing a rotation check
The columns it will create are:
id
- identifiercacheKey
- The unique cacke key, indexedtoken
- The encrypted tokenexpiration
- The expirationissued
- The issue datesubject
- The subject identifier
Custom Token Storage
If you would like to create your own token storage, just add your own WireBox ID to the driver
, properties
and implement the following interface: cbsecurity.interfaces.jwt.IJwtStorage
Last updated