hash_auth_wsc 1.0.0 → 1.0.3
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/lib/hash-auth/version.rb +1 -1
- metadata +5 -5
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: b342b7ce75cc0e9404cec85b58bbe1b978a5e2c1
|
4
|
+
data.tar.gz: 6a01a3dd63cd30b586d8bd03d540c34e49c99c21
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 3bf4ff9bb305aa042f43c4b59b0dd1885ea1e3007b0f887da1ab16716b0c7c4c57317143efb84e0262b844f91a4ec735ce0edbddcca9e9c9c9a2491318e523e0
|
7
|
+
data.tar.gz: 4e3ed5372c5103155fe08aaa65159c169b270fe6ea3bd41cbe494e1dfe7d40fdccd7339c8aada8fd57b440148379384ceee67576d1e04b898befa4c91ffa8d18
|
data/lib/hash-auth/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: hash_auth_wsc
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.0.
|
4
|
+
version: 1.0.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Max Lahey
|
@@ -28,16 +28,16 @@ dependencies:
|
|
28
28
|
name: rest-client
|
29
29
|
requirement: !ruby/object:Gem::Requirement
|
30
30
|
requirements:
|
31
|
-
- - "
|
31
|
+
- - ">="
|
32
32
|
- !ruby/object:Gem::Version
|
33
|
-
version: 1.
|
33
|
+
version: 1.8.0
|
34
34
|
type: :runtime
|
35
35
|
prerelease: false
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
37
37
|
requirements:
|
38
|
-
- - "
|
38
|
+
- - ">="
|
39
39
|
- !ruby/object:Gem::Version
|
40
|
-
version: 1.
|
40
|
+
version: 1.8.0
|
41
41
|
description: HashAuth allows your Rails application to support incoming and outgoing
|
42
42
|
two-factor authentication via hashing some component of an HTTPS request. Both sides
|
43
43
|
of the request (your Rails app and your client or provider) must have some unique
|