google-id-tokenz 1.2.1 → 1.2.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +5 -5
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: ba8107bf9c6ef5fa7ab7977fdba8212123c4021b
|
4
|
+
data.tar.gz: c8b6abe2090210aa1cd6ddfa92ddfe5e46042a91
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: cc476b5fe9aba5fe8960dc81169a3838cb3e7227b82fa667068fb41b556dcbfc2743d52c14d27189e5d67fb5282f253de9f8da8923f815a9f80ac28976ead21a
|
7
|
+
data.tar.gz: 83b3a4db506406f4a3ffc1eeb7fbb6b47290e9c27387ad5d2a0344bd98b7c3cd72eb88988deb20e285f51bcd172db0cc60a46a299844238b6982c441b36a4f98
|
data/README.md
CHANGED
@@ -1,10 +1,10 @@
|
|
1
1
|
# GoogleIDToken
|
2
2
|
|
3
|
-
This code is from [@timbray](https://github.com/timbray)'s awesome [google-id-token](https://code.google.com/p/google-id-token/) codebase, with one minor tweak to handle a new token format (array vs hash).
|
3
|
+
This code is from [@timbray](https://github.com/timbray)'s awesome [google-id-token](https://code.google.com/p/google-id-token/) codebase, with one minor tweak to handle a new token format (array vs hash).
|
4
4
|
|
5
|
-
Tim gives a great overview of id tokens here http://www.tbray.org/ongoing/When/201x/2013/04/04/ID-Tokens.
|
5
|
+
Tim gives a great overview of id tokens here http://www.tbray.org/ongoing/When/201x/2013/04/04/ID-Tokens.
|
6
6
|
|
7
|
-
GoogleIDToken currently provides a single useful class "Validator", which provides a single method "#check", which parses and validates an ID Token allegedly generated by Google auth servers.
|
7
|
+
GoogleIDToken currently provides a single useful class "Validator", which provides a single method "#check", which parses and validates an ID Token allegedly generated by Google auth servers.
|
8
8
|
|
9
9
|
## Examples
|
10
10
|
|
@@ -12,7 +12,7 @@ GoogleIDToken currently provides a single useful class "Validator", which provid
|
|
12
12
|
|
13
13
|
[android cross client auth](https://developers.google.com/accounts/docs/CrossClientAuth)
|
14
14
|
|
15
|
-
Creating a new validator takes a single optional hash argument. If the hash has an entry for :x509_key, that value is taken to be a key as created by OpenSSL::X509::Certificate.new, and the token is validated using that key. If there is no such entry, the keys are fetched from the Google certs endpoint https://www.googleapis.com/oauth2/v1/certs.
|
15
|
+
Creating a new validator takes a single optional hash argument. If the hash has an entry for :x509_key, that value is taken to be a key as created by OpenSSL::X509::Certificate.new, and the token is validated using that key. If there is no such entry, the keys are fetched from the Google certs endpoint https://www.googleapis.com/oauth2/v1/certs.
|
16
16
|
|
17
17
|
## Installation
|
18
18
|
|
@@ -20,7 +20,7 @@ Creating a new validator takes a single optional hash argument. If the hash has
|
|
20
20
|
gem install google-id-token
|
21
21
|
```
|
22
22
|
|
23
|
-
##
|
23
|
+
## Usage
|
24
24
|
|
25
25
|
```
|
26
26
|
validator = GoogleIDToken::Validator.new
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: google-id-tokenz
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.2.
|
4
|
+
version: 1.2.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Tim Bray
|
@@ -10,7 +10,7 @@ authors:
|
|
10
10
|
autorequire:
|
11
11
|
bindir: bin
|
12
12
|
cert_chain: []
|
13
|
-
date: 2014-08-
|
13
|
+
date: 2014-08-11 00:00:00.000000000 Z
|
14
14
|
dependencies:
|
15
15
|
- !ruby/object:Gem::Dependency
|
16
16
|
name: multi_json
|