knock-oauth2_code_verifier 0.1.1 → 0.1.2
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/knock-oauth2_code_verifier.gemspec +8 -8
- data/lib/knock/oauth2_code_verifier/version.rb +1 -1
- metadata +8 -8
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 674f83bd37cf5bdfdc9d2b311b4b9ca400e83e83d0ae74ef8dd922cbd3c9de26
|
|
4
|
+
data.tar.gz: cd9cd33b39f3fcb2961594eb4fb67becb6dc0b4f3e0dddf929b73e2c43a34bdc
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 71a615260d79dc8797b845ff0fd61572bd1af300bfd2db572672e9bbb8db6a2114e62eb82189eb7cc9f086cffeb430e4148bca15a2971f75e05c63b8218a415d
|
|
7
|
+
data.tar.gz: e7b185c1fa1e2e0d98c29e89a3ee91529a7f13f44812b8acb8373e487753b0f040bb1e29306d3b1d12b32d2c646f9a30db12c36cca84398b9bc662580b6db9b5
|
|
@@ -13,14 +13,14 @@ Gem::Specification.new do |spec|
|
|
|
13
13
|
spec.summary = "Backend provider of code verification for OAuth2\
|
|
14
14
|
Authorization Code Request"
|
|
15
15
|
spec.description = "Frontend libraries implement OAuth2 flows that \
|
|
16
|
-
authenticate the user with your SPA, but are only part of the picture. If
|
|
17
|
-
storing user data on a backend, you'll need to authenticate them on
|
|
18
|
-
frontend and the backend. That's what Oauth2 Authorization Code
|
|
19
|
-
with PKCE thrown in for added security. This gem provides the
|
|
20
|
-
authorization needed, taking in a verification request and logging the
|
|
21
|
-
via JWT with Knock. If you're using Vue/React/etc with a frontend
|
|
22
|
-
library like @nuxt/auth, and you're running Rails in API mode for
|
|
23
|
-
this gem completes the picture."
|
|
16
|
+
authenticate the user with your SPA, but are only part of the picture. If \
|
|
17
|
+
you're storing user data on a backend, you'll need to authenticate them on \
|
|
18
|
+
both the frontend and the backend. That's what Oauth2 Authorization Code \
|
|
19
|
+
Request does, with PKCE thrown in for added security. This gem provides the \
|
|
20
|
+
backend authorization needed, taking in a verification request and logging the \
|
|
21
|
+
user in via JWT with Knock. If you're using Vue/React/etc with a frontend \
|
|
22
|
+
authorization library like @nuxt/auth, and you're running Rails in API mode for \
|
|
23
|
+
your backend, this gem completes the picture."
|
|
24
24
|
spec.homepage = "https://github.com/recitalsoftware/knock-oauth2_code_verifier"
|
|
25
25
|
spec.license = "MIT"
|
|
26
26
|
spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: knock-oauth2_code_verifier
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.2
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Brendan Mulholland
|
|
@@ -53,13 +53,13 @@ dependencies:
|
|
|
53
53
|
- !ruby/object:Gem::Version
|
|
54
54
|
version: 1.4.0
|
|
55
55
|
description: Frontend libraries implement OAuth2 flows that authenticate the user
|
|
56
|
-
with your SPA, but are only part of the picture. If you'
|
|
57
|
-
backend, you'll need to authenticate them on both
|
|
58
|
-
what Oauth2 Authorization Code Request does,with PKCE thrown in for added
|
|
59
|
-
This gem provides the
|
|
60
|
-
and logging the user
|
|
61
|
-
frontend
|
|
62
|
-
for your backend,this gem completes the picture.
|
|
56
|
+
with your SPA, but are only part of the picture. If you're storing user data on
|
|
57
|
+
a backend, you'll need to authenticate them on both the frontend and the backend.
|
|
58
|
+
That's what Oauth2 Authorization Code Request does, with PKCE thrown in for added
|
|
59
|
+
security. This gem provides the backend authorization needed, taking in a verification
|
|
60
|
+
request and logging the user in via JWT with Knock. If you're using Vue/React/etc
|
|
61
|
+
with a frontend authorization library like @nuxt/auth, and you're running Rails
|
|
62
|
+
in API mode for your backend, this gem completes the picture.
|
|
63
63
|
email:
|
|
64
64
|
- brendan@recital.software
|
|
65
65
|
executables: []
|