jwt_signed_request 3.0.0 → 4.1.0
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/README.md +19 -1
- data/lib/jwt_signed_request/verify.rb +3 -0
- data/lib/jwt_signed_request/version.rb +1 -1
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: fec5e1348f0f1c6f1c0af31b3109b1a1602863f034f636bc9942852ea2c7cde9
|
4
|
+
data.tar.gz: e8efd84088c7b3ceb12db716606692d08d312ba89215a13a71062cefe6e3fc26
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 52792781ac61108ea1bbc1b4f3cb6d931012a16a10f5cfd6458b8250ad65413e2e15c1adcb490b968281b87ea60357a5886709457782e3fac31d9ca4f6d2c8b0
|
7
|
+
data.tar.gz: b86783098ab3c512d7eba496ea92e2c7c128ae9d103bd266ae7abbacf1e1ae25fb08e6503a8da02f54440a38bd7c679410fa46f7d9bf8f6db4c209b676d71aa5
|
data/README.md
CHANGED
@@ -1,5 +1,9 @@
|
|
1
1
|
# JWT Signed Request
|
2
|
-
|
2
|
+
|
3
|
+
[](https://github.com/envato/jwt_signed_request/blob/master/LICENSE.txt)
|
4
|
+
[](https://rubygems.org/gems/jwt_signed_request)
|
5
|
+
[](https://rubygems.org/gems/jwt_signed_request)
|
6
|
+
[](https://github.com/envato/jwt_signed_request/actions?query=branch%3Amaster+workflow%3Atests)
|
3
7
|
|
4
8
|
Request signing and verification for Internal APIs using JWT.
|
5
9
|
|
@@ -17,6 +21,14 @@ then run:
|
|
17
21
|
$ bundle
|
18
22
|
```
|
19
23
|
|
24
|
+
## Stale PRs
|
25
|
+
|
26
|
+
We use the "stale" workflow to manage our PRs.
|
27
|
+
If you have a PR open for 60 days without any activity, it will automatically be labelled `stale-pr`.
|
28
|
+
If there is no activity for 7 days after this label is applied, the PR will be automatically closed.
|
29
|
+
|
30
|
+
If you have a PR that has a sensible reason for being open for a long period of time with no activity, you can apply the `do-not-auto-close` label to avoid it being automatically closed.
|
31
|
+
|
20
32
|
## Generating EC Keys
|
21
33
|
|
22
34
|
We should be using a public key encryption algorithm such as **ES256**. To generate your public/private key pair using **ES256** run:
|
@@ -287,6 +299,12 @@ Configured versions are defined in [Appraisals](./Appraisals), which at time of
|
|
287
299
|
].each do |jwt_version|
|
288
300
|
```
|
289
301
|
|
302
|
+
Ensure you set up your local environment by running:
|
303
|
+
|
304
|
+
```sh
|
305
|
+
bundle exec appraisal install
|
306
|
+
```
|
307
|
+
|
290
308
|
Run the test suite like this:
|
291
309
|
|
292
310
|
```sh
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: jwt_signed_request
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version:
|
4
|
+
version: 4.1.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Envato
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date:
|
11
|
+
date: 2025-06-25 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: jwt
|
@@ -161,7 +161,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
161
161
|
- !ruby/object:Gem::Version
|
162
162
|
version: '0'
|
163
163
|
requirements: []
|
164
|
-
rubygems_version: 3.
|
164
|
+
rubygems_version: 3.5.16
|
165
165
|
signing_key:
|
166
166
|
specification_version: 4
|
167
167
|
summary: JWT request signing and verification for Internal APIs
|