warden-jwt_auth 0.10.0 → 0.10.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -3
- data/README.md +1 -1
- data/lib/warden/jwt_auth/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 60f3a20e896744f9907bae893ef869cebf5240e3250c98ea9e642aee65f69971
|
|
4
|
+
data.tar.gz: c3fcb1ebf73d1553d8b91c2195b465095ed9b0cf888ccf0a4474f6ccbba7329e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: a7a29ff7471a33da771a5a5ace1906e7e017aa3640f79779d1cd42c8edf1e52d2c3470489021c4826eefa7bf4023135260347cc004a2df9ddfcdb639a3fa0dfe
|
|
7
|
+
data.tar.gz: d9192d67594cc4f86392b5d45b3f41ed13e7321cc52406168f9edb073bcc985c384252000713c20294c6a38ed8fe8960ff544216cd73f9a3c74447050c8176a7
|
data/CHANGELOG.md
CHANGED
|
@@ -4,10 +4,10 @@ All notable changes to this project will be documented in this file.
|
|
|
4
4
|
The format is based on [Keep a Changelog](http://keepachangelog.com/)
|
|
5
5
|
and this project adheres to [Semantic Versioning](http://semver.org/).
|
|
6
6
|
|
|
7
|
-
## [0.10.
|
|
8
|
-
-
|
|
7
|
+
## [0.10.1] - 2024-12-15
|
|
8
|
+
- Fix version mismatch
|
|
9
9
|
|
|
10
|
-
## [0.
|
|
10
|
+
## [0.8.0] - 2024-06-28
|
|
11
11
|
- Add support for issue claim ([56](https://github.com/waiting-for-dev/warden-jwt_auth/pull/56))
|
|
12
12
|
|
|
13
13
|
## [0.8.0] - 2023-01-31
|
data/README.md
CHANGED
|
@@ -175,7 +175,7 @@ config.revocation_strategies = { user: RevocationStrategy }
|
|
|
175
175
|
|
|
176
176
|
The implementation of the revocation strategy is also on your side. They just need to implement two methods: `jwt_revoked?` and `revoke_jwt`, both of them accepting as parameters the JWT payload and the user record, in this order.
|
|
177
177
|
|
|
178
|
-
You can read about which [JWT recovation strategies](http://waiting-for-dev.github.io/blog/2017/01/24/jwt_revocation_strategies
|
|
178
|
+
You can read about which [JWT recovation strategies](http://waiting-for-dev.github.io/blog/2017/01/24/jwt_revocation_strategies) can be implement with their pros and cons.
|
|
179
179
|
|
|
180
180
|
```ruby
|
|
181
181
|
module RevocationStrategy
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: warden-jwt_auth
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.10.
|
|
4
|
+
version: 0.10.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Marc Busqué
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2024-
|
|
11
|
+
date: 2024-12-15 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: dry-auto_inject
|