umeng_verify 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +8 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +4 -0
- data/LICENSE.txt +21 -0
- data/README.md +43 -0
- data/Rakefile +2 -0
- data/bin/console +14 -0
- data/bin/setup +8 -0
- data/lib/umeng_verify.rb +15 -0
- data/lib/umeng_verify/client.rb +70 -0
- data/lib/umeng_verify/version.rb +3 -0
- data/umeng_verify.gemspec +27 -0
- metadata +83 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 49621ab0ce0ae938ec13d699d42482bc35aa825cfc6c36fb29d6ba9ee4116052
|
4
|
+
data.tar.gz: fad3330bcab8e2f7325572e21721bdef5f401716b82b3e163aa872618eb9590d
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 7fa6e0c9ea7ec5673f3a3f9dd5f716b7eef7c7d9192c06b8b27579be8e549504a647669aca92c9b2f5f5779dcfb1b3b66193685e69922f9fd062b1de3fd32db1
|
7
|
+
data.tar.gz: eb6328fd1359e77c933eb843158c8a7d288f99c0f66e0df04734c67771845c779872b77345679d666ed4c9f6e37913cc6f22cb3c0b3a3a5d02b9da808bd8659c
|
data/.gitignore
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at xxy@xuxiangyang.com. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2020 xuxiangyang
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,43 @@
|
|
1
|
+
# UmengVerify
|
2
|
+
|
3
|
+
Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/umeng_verify`. To experiment with that code, run `bin/console` for an interactive prompt.
|
4
|
+
|
5
|
+
TODO: Delete this and the text above, and describe your gem
|
6
|
+
|
7
|
+
## Installation
|
8
|
+
|
9
|
+
Add this line to your application's Gemfile:
|
10
|
+
|
11
|
+
```ruby
|
12
|
+
gem 'umeng_verify'
|
13
|
+
```
|
14
|
+
|
15
|
+
And then execute:
|
16
|
+
|
17
|
+
$ bundle
|
18
|
+
|
19
|
+
Or install it yourself as:
|
20
|
+
|
21
|
+
$ gem install umeng_verify
|
22
|
+
|
23
|
+
## Usage
|
24
|
+
|
25
|
+
TODO: Write usage instructions here
|
26
|
+
|
27
|
+
## Development
|
28
|
+
|
29
|
+
After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
30
|
+
|
31
|
+
To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
|
32
|
+
|
33
|
+
## Contributing
|
34
|
+
|
35
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/umeng_verify. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
36
|
+
|
37
|
+
## License
|
38
|
+
|
39
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
40
|
+
|
41
|
+
## Code of Conduct
|
42
|
+
|
43
|
+
Everyone interacting in the UmengVerify project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/umeng_verify/blob/master/CODE_OF_CONDUCT.md).
|
data/Rakefile
ADDED
data/bin/console
ADDED
@@ -0,0 +1,14 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "umeng_verify"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
10
|
+
# require "pry"
|
11
|
+
# Pry.start
|
12
|
+
|
13
|
+
require "irb"
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
ADDED
data/lib/umeng_verify.rb
ADDED
@@ -0,0 +1,15 @@
|
|
1
|
+
require "umeng_verify/version"
|
2
|
+
require "umeng_verify/client"
|
3
|
+
|
4
|
+
module UmengVerify
|
5
|
+
class Error < StandardError; end
|
6
|
+
class ResponseError < Error
|
7
|
+
attr_accessor :code, :request_id, :message
|
8
|
+
def initialize(code, request_id, message)
|
9
|
+
@code = code
|
10
|
+
@request_id = request_id
|
11
|
+
@message = message
|
12
|
+
super("Bad Response with #{code}, message=#{message}")
|
13
|
+
end
|
14
|
+
end
|
15
|
+
end
|
@@ -0,0 +1,70 @@
|
|
1
|
+
require 'securerandom'
|
2
|
+
require 'uri'
|
3
|
+
require 'digest'
|
4
|
+
require 'json'
|
5
|
+
require 'openssl'
|
6
|
+
require 'net/http'
|
7
|
+
require 'net/https'
|
8
|
+
require 'base64'
|
9
|
+
module UmengVerify
|
10
|
+
class Client
|
11
|
+
attr_accessor :app_secret, :app_key, :host, :http
|
12
|
+
def initialize(app_key, app_secret)
|
13
|
+
@app_secret = app_secret
|
14
|
+
@app_key = app_key
|
15
|
+
@host = "verify5.market.alicloudapi.com"
|
16
|
+
@http = Net::HTTP.new(@host, 443)
|
17
|
+
@http.use_ssl = true
|
18
|
+
end
|
19
|
+
|
20
|
+
def info(token)
|
21
|
+
request("POST", "/api/v1/mobile/info", token: token)
|
22
|
+
end
|
23
|
+
|
24
|
+
def verify(token, phone_number)
|
25
|
+
request("POST", "/api/v1/mobile/verify", token: token, phoneNumber: phone_number)
|
26
|
+
end
|
27
|
+
|
28
|
+
def request(method, path, body = {}, headers = {})
|
29
|
+
headers["Content-Type"] = "application/json; charset=UTF-8"
|
30
|
+
headers["Accept"] = "application/json"
|
31
|
+
headers["Content-MD5"] = Base64.strict_encode64(Digest::MD5.digest(JSON.dump(body)))
|
32
|
+
headers["Date"] = Time.now.gmtime.strftime("%a, %d %b %Y %H:%M:%S GMT")
|
33
|
+
headers["X-Ca-Version"] = "1"
|
34
|
+
headers["X-Ca-Stage"] = "RELEASE"
|
35
|
+
headers["X-Ca-Key"] = app_key
|
36
|
+
headers["X-Ca-Timestamp"] = (Time.now.to_f * 1000).to_i.to_s
|
37
|
+
headers["X-Ca-Nonce"] = SecureRandom.hex
|
38
|
+
|
39
|
+
query = URI(path).query
|
40
|
+
form = query ? URI.decode_www_form(query).to_h : {}
|
41
|
+
|
42
|
+
signature_headers = ["X-Ca-Version", "X-Ca-Stage", "X-Ca-Key", "X-Ca-Timestamp", "X-Ca-Nonce"].sort
|
43
|
+
|
44
|
+
string_to_sign = [
|
45
|
+
method,
|
46
|
+
headers["Accept"],
|
47
|
+
headers["Content-MD5"],
|
48
|
+
headers["Content-Type"],
|
49
|
+
headers["Date"],
|
50
|
+
signature_headers.map { |k| "#{k}:#{headers[k]}" }.join("\n"),
|
51
|
+
form.empty? ? path : "#{path}?#{form.sort.map { |k, v| "#{k}=#{v}" }.join('&')}",
|
52
|
+
].join("\n")
|
53
|
+
|
54
|
+
headers["X-Ca-Signature"] = Base64.strict_encode64(OpenSSL::HMAC.digest("SHA256", app_secret, string_to_sign))
|
55
|
+
headers["X-Ca-Signature-Headers"] = signature_headers.join(",")
|
56
|
+
|
57
|
+
if method == Net::HTTP::Get::METHOD
|
58
|
+
request = Net::HTTP::Get.new(path, headers)
|
59
|
+
else
|
60
|
+
request = Net::HTTP::Post.new(path, headers)
|
61
|
+
request.body = JSON.dump(body)
|
62
|
+
end
|
63
|
+
|
64
|
+
resp = http.request(request)
|
65
|
+
raise ResponseError.new(resp.code.to_i, resp["X-Ca-Request-Id"], resp["X-Ca-Error-Message"]) unless resp.code.to_i == 200
|
66
|
+
|
67
|
+
JSON.parse(resp.body)
|
68
|
+
end
|
69
|
+
end
|
70
|
+
end
|
@@ -0,0 +1,27 @@
|
|
1
|
+
lib = File.expand_path("../lib", __FILE__)
|
2
|
+
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
3
|
+
require "umeng_verify/version"
|
4
|
+
|
5
|
+
Gem::Specification.new do |spec|
|
6
|
+
spec.name = "umeng_verify"
|
7
|
+
spec.version = UmengVerify::VERSION
|
8
|
+
spec.authors = ["xuxiangyang"]
|
9
|
+
spec.email = ["xxy@xuxiangyang.com"]
|
10
|
+
|
11
|
+
spec.summary = %q{Umeng 智能认证U-Verify ruby gem}
|
12
|
+
spec.description = %q{Umeng 智能认证U-Verify ruby gem}
|
13
|
+
spec.homepage = "http://github.com/xuxiangyang/umeng_verify"
|
14
|
+
spec.license = "MIT"
|
15
|
+
|
16
|
+
# Specify which files should be added to the gem when it is released.
|
17
|
+
# The `git ls-files -z` loads the files in the RubyGem that have been added into git.
|
18
|
+
spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
|
19
|
+
`git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
|
20
|
+
end
|
21
|
+
spec.bindir = "exe"
|
22
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
23
|
+
spec.require_paths = ["lib"]
|
24
|
+
|
25
|
+
spec.add_development_dependency "bundler", "~> 2.0"
|
26
|
+
spec.add_development_dependency "rake", "~> 10.0"
|
27
|
+
end
|
metadata
ADDED
@@ -0,0 +1,83 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: umeng_verify
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.1.1
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- xuxiangyang
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2020-01-03 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: bundler
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - "~>"
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '2.0'
|
20
|
+
type: :development
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - "~>"
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '2.0'
|
27
|
+
- !ruby/object:Gem::Dependency
|
28
|
+
name: rake
|
29
|
+
requirement: !ruby/object:Gem::Requirement
|
30
|
+
requirements:
|
31
|
+
- - "~>"
|
32
|
+
- !ruby/object:Gem::Version
|
33
|
+
version: '10.0'
|
34
|
+
type: :development
|
35
|
+
prerelease: false
|
36
|
+
version_requirements: !ruby/object:Gem::Requirement
|
37
|
+
requirements:
|
38
|
+
- - "~>"
|
39
|
+
- !ruby/object:Gem::Version
|
40
|
+
version: '10.0'
|
41
|
+
description: Umeng 智能认证U-Verify ruby gem
|
42
|
+
email:
|
43
|
+
- xxy@xuxiangyang.com
|
44
|
+
executables: []
|
45
|
+
extensions: []
|
46
|
+
extra_rdoc_files: []
|
47
|
+
files:
|
48
|
+
- ".gitignore"
|
49
|
+
- CODE_OF_CONDUCT.md
|
50
|
+
- Gemfile
|
51
|
+
- LICENSE.txt
|
52
|
+
- README.md
|
53
|
+
- Rakefile
|
54
|
+
- bin/console
|
55
|
+
- bin/setup
|
56
|
+
- lib/umeng_verify.rb
|
57
|
+
- lib/umeng_verify/client.rb
|
58
|
+
- lib/umeng_verify/version.rb
|
59
|
+
- umeng_verify.gemspec
|
60
|
+
homepage: http://github.com/xuxiangyang/umeng_verify
|
61
|
+
licenses:
|
62
|
+
- MIT
|
63
|
+
metadata: {}
|
64
|
+
post_install_message:
|
65
|
+
rdoc_options: []
|
66
|
+
require_paths:
|
67
|
+
- lib
|
68
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
69
|
+
requirements:
|
70
|
+
- - ">="
|
71
|
+
- !ruby/object:Gem::Version
|
72
|
+
version: '0'
|
73
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
74
|
+
requirements:
|
75
|
+
- - ">="
|
76
|
+
- !ruby/object:Gem::Version
|
77
|
+
version: '0'
|
78
|
+
requirements: []
|
79
|
+
rubygems_version: 3.0.6
|
80
|
+
signing_key:
|
81
|
+
specification_version: 4
|
82
|
+
summary: Umeng 智能认证U-Verify ruby gem
|
83
|
+
test_files: []
|