omniauth-github-team-member 2.0.1 → 2.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 218e0ef9988beea2c34414714e37f626a224d305
-  data.tar.gz: 46178d0fad6e6566dce9973038b4f6f1ee544acd
+SHA256:
+  metadata.gz: 2ac1491bf37b9186f206e2fe303e55090a1835f981dfe93519db775c38d21ad2
+  data.tar.gz: 41d42aa061dff7acee04796abf49425ad3b6dd4245e513c4a02a57b6f9b3f10a
 SHA512:
-  metadata.gz: faf45019bf739e983db8e7a312db8541f5d2c60e4abb3adb5271fc9050c0fc2584c5ee6251b77dc1f5bf276dbc2ea506ffc1442a125b3bd618b185ef48de5f15
-  data.tar.gz: e0aff5d84e5cde4b92895249dc1930f51d50dd2408810bf731e7df0233661f8489e3af13e0acabfeef29930a8c02ac7f35b5f0a92253780854ba3f2f046abb5f
+  metadata.gz: e4b226fa970d2d5a63ebf4e764021b10b049081bdcb63f2f9cea347fba279451f2236c9d472363509e41458ca06b22ec246ce56c139bffa43fc2131fd97d1474
+  data.tar.gz: f51c34abc78c5434471d684d67a281ca4c2513e4916af5b1b4a7e59caa6d016d60c7d5a5094e8ee0c5f23d5d9448d986b418b2dd251ef975b8fc1448f10d880c

data/README.md

@@ -16,25 +16,27 @@ I like to store the GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET in my environment,
 
 ## Basic Usage
 
+In the examples below, `42634` is the id of the team we are checking against. You can find the id of a team via the GitHub API, either by [listing all teams for the parent org](https://developer.github.com/v3/orgs/teams/#list-teams) or [finding all of the team memberships for a user who is on the team you are looking for](https://developer.github.com/v3/orgs/teams/#get-team-membership).
+
 Usage in Rails:
 
 ```ruby
+# config/initializers/github_omniauth.rb
+
 Rails.application.config.middleware.use OmniAuth::Builder do
   provider :githubteammember,
     ENV['GITHUB_CLIENT_ID'],
     ENV['GITHUB_CLIENT_SECRET'],
-    :scope => 'user',
-    :teams => {
+    scope: 'read:org',
+    teams: {
       "mentors_team_member?" => 426344
     }
 end
 ```
 
-During the callback phase, you can check to see if the authed user is on the mentors team or not
-by checking the returned credentials object `request.env['omniauth.auth'].credentials.mentors_team_member?`.
+During the callback phase, you can check to see if the authed user is on the mentors team or not by checking the returned credentials object `request.env['omniauth.auth'].credentials.mentors_team_member?`.
 
-An example of how to integrate this strategy with OmniAuth is below. Do note that these
-examples are just guidelines, you will most likely need to change each example to match your application's needs.
+An example of how to integrate this strategy with OmniAuth is below. Do note that these examples are just guidelines, you will most likely need to change each example to match your application's needs.
 
 ```ruby
 class SessionsController
@@ -81,8 +83,8 @@ use OmniAuth::Builder do
   provider :githubteammember,
     ENV['GITHUB_CLIENT_ID'],
     ENV['GITHUB_CLIENT_SECRET'],
-    :scope => 'user',
-    :teams => {
+    scope: 'read:org',
+    teams: {
       "mentors_team_member?" => 426344
     }
 end
@@ -90,8 +92,7 @@ end
 
 ### Scopes
 
-You must require the user scope to be able to access the team data associated with
-the authenticated user.
+You must require the `read:org` scope to be able to access the team data associated with the authenticated user.
 
 More info on [Scopes](http://developer.github.com/v3/oauth/#scopes).
 
@@ -108,3 +109,6 @@ More info on [Scopes](http://developer.github.com/v3/oauth/#scopes).
 * [Garrett Bjerkhoel](https://github.com/dewski)
 * [Jonathan Hoyt](https://github.com/jonmagic)
 * [Arthur Chiu](https://github.com/achiu)
+* [Tim Clem](https://github.com/tclem)
+* [Jessie Young](https://github.com/jessieay)
+* [Paul Schreiber](https://github.com/paulschreiber)

data/lib/omniauth-github-team-member/version.rb

@@ -1,5 +1,5 @@
 module OmniAuth
   module GitHubTeamMember
-    VERSION = '2.0.1'
+    VERSION = '2.1.0'
   end
 end

data/lib/omniauth/strategies/github_team_member.rb

@@ -7,10 +7,18 @@ module OmniAuth
         options['teams'].inject({}) do |base, key_value_pair|
           method_name, team_id = key_value_pair
           base[booleanize_method_name(method_name)] = team_member?(team_id)
+          base["email"] = email_addresses
           base
         end
       end
 
+      def email_addresses
+        response = access_token.get("/user/emails")
+        response.status == 200 && response.parsed.map{|user| user["email"]}
+      rescue ::OAuth2::Error
+        false
+      end
+
       def team_member?(team_id)
         response = access_token.get("/teams/#{team_id}/memberships/#{raw_info['login']}")
         response.status == 200 && response.parsed["state"] == "active"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-github-team-member
 version: !ruby/object:Gem::Version
-  version: 2.0.1
+  version: 2.1.0
 platform: ruby
 authors:
 - Garrett Bjerkhoel
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-11-25 00:00:00.000000000 Z
+date: 2021-02-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: omniauth-github
@@ -121,8 +121,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 3.0.3
 signing_key: 
 specification_version: 4
 summary: OmniAuth strategy for GitHub Team Auth.