wcc-auth 0.7.0 → 0.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 18b674d08200f15499cccd1b8d1fd99916d7c744
-  data.tar.gz: 18eda6bc05124affbc80279597935104589edb41
+  metadata.gz: d3c7e9259c716d32bb56f4e6b7da678bdc9d158b
+  data.tar.gz: 60b330ef71e4327cfbc992148dff79474baf3624
 SHA512:
-  metadata.gz: cf2801c9dc386cffa8535ad5b91dac36362bd5e30126a36bee4259955a0ac289534156a55dd59b796333848107f831421f3cf2a6e4ebce3c18a3a9a0d2e507df
-  data.tar.gz: '09706c0b7f3a3a891f28b8005671436d4f5090c2fbc52890158e4f407f655e45f085193922063cd872824ccafd2941fde50bae9af8d49fc98cc565241d86d409'
+  metadata.gz: 328b4bf8ef14bd065f3d0fab25c394229387d87718ddb86b97bf18e4d234818df02177aa2a578ea42c82c2666c31f176d233854e6e4b735083640a9188e0cde0
+  data.tar.gz: 5621686cb846090c6295f1367091d04e8f31726740e12febb3110b23d704ebff64ef43557773c15b989ea01c9f070a8b476ed61cb8edbc5abcbb579b9762b769

data/README.md

@@ -56,10 +56,8 @@ end
 ```ruby
 class User < ActiveRecord::Base
   include WCC::Auth::Providers::ActiveRecord
-  devise :omniauthable
-
+  devise :omniauthable, omniauth_providers: %i[watermark]
   # ...
-
 end
 ```
 

data/lib/wcc/auth/devise/watermark_callbacks_controller.rb

@@ -2,11 +2,11 @@ class WCC::Auth::Devise::WatermarkCallbacksController < Devise::OmniauthCallback
   skip_authorization_check if respond_to?(:skip_authorization_check)
 
   def watermark
-    oauth_data = request.env["omniauth.auth"]
+    oauth_data = request.env['omniauth.auth']
     @user = User.initialize_from_watermark_oauth(oauth_data)
     @user.save
 
-    sign_in_and_redirect @user
+    sign_in_and_redirect @user, event: :authentication
   end
 
   def failure
@@ -21,6 +21,4 @@ class WCC::Auth::Devise::WatermarkCallbacksController < Devise::OmniauthCallback
   def after_omniauth_failure_path_for(scope)
     root_path
   end
-
 end
-

data/lib/wcc/auth/version.rb

@@ -1,5 +1,5 @@
 module WCC
   module Auth
-    VERSION = '0.7.0'.freeze
+    VERSION = '0.7.1'.freeze
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: wcc-auth
 version: !ruby/object:Gem::Version
-  version: 0.7.0
+  version: 0.7.1
 platform: ruby
 authors:
 - Watermark Dev
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-11-29 00:00:00.000000000 Z
+date: 2018-03-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cancancan
@@ -180,29 +180,29 @@ summary: '# WCC::Auth  Provides the necessary tools for handling authentication
   your controllers  ```ruby # Add this include to your ApplicationController class
   ApplicationController < ActionController::Base include WCC::Auth::ControllerHelpers
   end ```  #### Setup your user model  ```ruby class User < ActiveRecord::Base include
-  WCC::Auth::Providers::ActiveRecord devise :omniauthable  # ...  end ```  #### Setup
-  authorization (optional)  If you would like to use the `TieredAbility` class included
-  with `WCC::Auth` just create an Ability class that extends the `WCC::Auth::TieredAbility`
-  class. The authenticated user will include an info variables called `access_level_id`.
-  This corresponds to a `WCC::Auth::AccessLevel`.  The access levels are broken down
-  into 5 tiers with the following rules:  * **No access** -- This is the default level
-  * **Basic** -- This is provides read-only access * **Contribute** -- Read-write
-  for only data the user owns * **Manage** -- Read-write for other''s data * **App
-  Admin** -- Can change app configuration * **System Admin** -- Has full access to
-  all features always  Each tier inherits all priveleges of the lower tiers. The rules
-  here are guidelines for the app to follow. It is ultimately up to the client application
-  to decide what each of these tiers means for it. Do your best to adhere to these
-  rules.  Here is an example Ability class using the DSL provided by `WCC::Auth`.  ```ruby
-  class Ability < WCC::Auth::TieredAbility at_level(:contribute) do |user| can :read,
-  Person can :manage, Task, created_by_id: user.id can :manage, Comment, created_by_id:
-  user.id  cannot :destroy, Task end  at_level(:appadmin) do |user| can :manage, :all
-  cannot :create, TaskGroup end   at_level(:sysadmin) do |user| can :manage, :all
-  end end ```  ## Notes  #### Sign out links  If your project is using `TurboLinks`,
-  you''ll need to disable it for the sign out link(s). Otherwise, it will cause your
-  app to enter an infinite redirect loop.  ## Contributing  1. Fork it 2. Create your
-  feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit
-  -am ''Add some feature''`) 4. Push to the branch (`git push origin my-new-feature`)
-  5. Create new Pull Request'
+  WCC::Auth::Providers::ActiveRecord devise :omniauthable, omniauth_providers: %i[watermark]
+  # ... end ```  #### Setup authorization (optional)  If you would like to use the
+  `TieredAbility` class included with `WCC::Auth` just create an Ability class that
+  extends the `WCC::Auth::TieredAbility` class. The authenticated user will include
+  an info variables called `access_level_id`. This corresponds to a `WCC::Auth::AccessLevel`.  The
+  access levels are broken down into 5 tiers with the following rules:  * **No access**
+  -- This is the default level * **Basic** -- This is provides read-only access *
+  **Contribute** -- Read-write for only data the user owns * **Manage** -- Read-write
+  for other''s data * **App Admin** -- Can change app configuration * **System Admin**
+  -- Has full access to all features always  Each tier inherits all priveleges of
+  the lower tiers. The rules here are guidelines for the app to follow. It is ultimately
+  up to the client application to decide what each of these tiers means for it. Do
+  your best to adhere to these rules.  Here is an example Ability class using the
+  DSL provided by `WCC::Auth`.  ```ruby class Ability < WCC::Auth::TieredAbility at_level(:contribute)
+  do |user| can :read, Person can :manage, Task, created_by_id: user.id can :manage,
+  Comment, created_by_id: user.id  cannot :destroy, Task end  at_level(:appadmin)
+  do |user| can :manage, :all cannot :create, TaskGroup end   at_level(:sysadmin)
+  do |user| can :manage, :all end end ```  ## Notes  #### Sign out links  If your
+  project is using `TurboLinks`, you''ll need to disable it for the sign out link(s).
+  Otherwise, it will cause your app to enter an infinite redirect loop.  ## Contributing  1.
+  Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit
+  your changes (`git commit -am ''Add some feature''`) 4. Push to the branch (`git
+  push origin my-new-feature`) 5. Create new Pull Request'
 test_files:
 - spec/spec_helper.rb
 - spec/wcc/auth/access_level_spec.rb