omniauth-mit-oauth2 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3db752ef555c3cd5fca32ffdc4d3d010e7c07f6e
-  data.tar.gz: 25dba93846917189125f28dca41537ea59bdb7fe
+  metadata.gz: 9675cfb77481115bbd2d5d8e6b385812a265a78d
+  data.tar.gz: 87956af5a93f5dd135796aa0220ed723229bd96f
 SHA512:
-  metadata.gz: b33cfc0a214b90ae5c1e125e372ddfb8ffba3067380800a23a9080be9bc4f539ce8e2fa358816704d1df1ba4dcc846ac7d79971f9692ce5e0bd0625d108f7c6f
-  data.tar.gz: 87253db41e8c22ceacd6dfa731cb8a40dc0627a7bf5f9b3f24eebba24757502c704293fdd7ff3c4516b70de34c22ad82391667e02c5d0e47387c1de3b360c7de
+  metadata.gz: a4ddacb9bb4bd9c7e82796ba01c220b31b51b28169b5c93a94e726d0c66dce3549f8a7fa59e9bd180c62a9009e288db4f9f902b3d0d18d44c0f3db4c9ad261b6
+  data.tar.gz: e1dab8b8de9e2de4eb4f60877feeb7de18206c070599aa424af3fd070c9f8b7f6b6a81709cb846097ed084eb05e68d00221b49cc2d02a5af02fd67ccf01e5934

data/README.md

@@ -2,6 +2,8 @@
 
 This gem provides an OmniAuth strategy for authenticating users through [MIT OpenID Connect](https://oidc.mit.edu/).
 
+[![Gem Version](https://badge.fury.io/rb/omniauth-mit-oauth2.svg)](https://badge.fury.io/rb/omniauth-mit-oauth2)
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -27,9 +29,10 @@ Rails.application.config.middleware.use OmniAuth::Builder do
   provider :mit_oauth2, "MIT_OAUTH2_API_KEY", "MIT_OAUTH2_API_SECRET", {
     scope: "openid,name,email"
   }
+end
 ```
 
-Replace `MIT_OAUTH2_API_KEY` and `MIT_OAUTH2_API_SECRET` with the values obtained from registering your service through MIT OIDC.
+Replace `MIT_OAUTH2_API_KEY` and `MIT_OAUTH2_API_SECRET` with the values obtained from registering your service through MIT OIDC. You generally want to keep those out of version control so populate the values however you are handling secrets in your app.
 
 ## Devise
 
@@ -108,7 +111,7 @@ Devise.setup do |config|
 end
 ```
 
-Replace `MIT_OAUTH2_API_KEY` and `MIT_OAUTH2_API_SECRET` with the values obtained by registering your site.
+Replace `MIT_OAUTH2_API_KEY` and `MIT_OAUTH2_API_SECRET` with the values obtained by registering your site through MIT OIDC. You generally want to keep those out of version control so populate the values however you are handling secrets in your app.
 
 Now we need to set up the routes:
 
@@ -175,4 +178,3 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/MITLib
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
-

data/lib/omniauth/mit_oauth2/version.rb

@@ -1,5 +1,5 @@
 module OmniAuth
   module MITOAuth2
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

data/lib/omniauth/strategies/mit_oauth2.rb

@@ -24,6 +24,10 @@ module OmniAuth
         { raw_info: raw_info }
       end
 
+      def callback_url
+        full_host + script_name + callback_path
+      end
+
       def raw_info
         @raw_info ||= access_token.get('/userinfo').parsed
       end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-mit-oauth2
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Mike Graves
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-11 00:00:00.000000000 Z
+date: 2015-12-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: omniauth-oauth2
@@ -105,8 +105,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5
+rubygems_version: 2.4.5.1
 signing_key: 
 specification_version: 4
 summary: OmniAuth strategy for MIT OIDC
 test_files: []
+has_rdoc: