Releases: zaikio/zaikio-jwt_auth
Releases · zaikio/zaikio-jwt_auth
v.2.1.1
v2.1.0
v2.0.0
- BREAKING
config.redis
has been replaced withconfig.cache
, replacing the
direct Redis dependency with an instance of aActiveSupport::Cache::Store
. If you
wish to keep using Redis, you should wrap it like so:
-config.redis = Redis.new
+config.cache = ActiveSupport::Cache::RedisCacheStore.new
Alternatively, you can also use Rails.cache
to use a different backend:
-config.redis = Redis.new
+config.cache = Rails.cache
v1.0.2
- After setting
authorize_by_jwt_subject_type
andauthorize_by_jwt_scopes
in a controller, any classes inheriting from your controller will also get a copy of those attributes. You can override this behaviour by calling the methods again in the child class.
v1.0.1
- Bugfix: add runtime dependency
activejob
for rebuilding theDirectoryCache
v1.0.0
- BREAKING When updating the
DirectoryCache
(either usinginvalidate: true
or when the cache expires), it will no longer retry & sleep, blocking the main thread. Instead, it enqueues a background job to attempt the update (and will re-queue again, if needed, until the job succeeds.
v0.5.1
This is a bugfix release, please upgrade from v0.5.0 as soon as possible:
- Set correct
use_ssl
flag onnet/http
when working with HTTPS connections
v0.5.0
- Throw a
Zaikio::JWTAuth::DirectoryCache::BadResponseError
when the server returns with an unexpected HTTP 4xx error code or non-JSON body.
v0.4.4
[0.4.4] - 2020-03-25
- Replace dependency on
rails
with a more specific dependency onrailties
v0.4.3
- Fix incorrect const_defined? behaviour when initializing without zaikio-webhooks gem