wcc-auth 0.6.0 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fb6bf890e98d60f40cdebab2cb97ba9ef70e7101
-  data.tar.gz: 9bb463bc83d2741b9059a04ce466e6e668827485
+  metadata.gz: 18b674d08200f15499cccd1b8d1fd99916d7c744
+  data.tar.gz: 18eda6bc05124affbc80279597935104589edb41
 SHA512:
-  metadata.gz: 2d7c384ce1f02d9c9c29bda115c97533441390e33fd3f1816b50ec13d39005fc1ca2e5412891a290d4d45d3a9415ed2b3bdf46f10731bf0eb28119114c240eee
-  data.tar.gz: b4d12bc4ea9ba9e607027f79af898ef2185c7144f67061185a963a71eb84cc02ea726092ed9d33b0164f7c0cfe25a6cf1896f172dabf9c45b49452cfd71fbf98
+  metadata.gz: cf2801c9dc386cffa8535ad5b91dac36362bd5e30126a36bee4259955a0ac289534156a55dd59b796333848107f831421f3cf2a6e4ebce3c18a3a9a0d2e507df
+  data.tar.gz: '09706c0b7f3a3a891f28b8005671436d4f5090c2fbc52890158e4f407f655e45f085193922063cd872824ccafd2941fde50bae9af8d49fc98cc565241d86d409'

data/README.md

@@ -8,6 +8,8 @@ any Ruby project. Currently, the only tested path is Rails with Devise.
 
 ## Installation
 
+**NOTE: `v0.6.0` has been updated for use with Rails 5.1 and requires Ruby 2.2 or greater.**
+
 Add this line to your application's Gemfile:
 
 ```ruby
@@ -107,6 +109,12 @@ class Ability < WCC::Auth::TieredAbility
 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

data/lib/omniauth/strategies/watermark.rb

@@ -19,6 +19,7 @@ class OmniAuth::Strategies::Watermark < OmniAuth::Strategies::OAuth2
       last_name: raw_info["last_name"],
       access_level_id: raw_info["access_level_id"],
       arena_id: raw_info["arena_id"],
+      rock_id: raw_info["rock_id"],
       applications: raw_info["applications"]
     }
   end

data/lib/wcc/auth/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: wcc-auth
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.7.0
 platform: ruby
 authors:
 - Watermark Dev
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-05-26 00:00:00.000000000 Z
+date: 2017-11-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cancancan
@@ -166,36 +166,40 @@ summary: '# WCC::Auth  Provides the necessary tools for handling authentication
   Watermark''s OAuth provider as well as authorizing the user has access to specific
   features within the application. There are special hooks for Rails apps using Devise,
   but the primitive structures could be used on any Ruby project. Currently, the only
-  tested path is Rails with Devise.  ## Installation  Add this line to your application''s
-  Gemfile:  ```ruby gem ''wcc-auth'', ''~> 0.3.2'' ```  If you are using a Rails app
-  with Devise you can use a special require hook that will setup all the Devise specific
-  configuration for you.  ```ruby gem ''wcc-auth'', ''~> 0.3.2'', require: ''wcc/auth/devise''
-  ```  ## Configuration  There are a few steps to setup your app. These instructions
-  are specific to a Rails app.  #### Add the configuration block to an initializer  In
-  order to configure the gem you must run the `WCC::Auth.setup` block. See below for
-  an example:  ```ruby WCC::Auth.setup do |config| config.app_name = "app-name" config.environment
-  = Rails.env config.app_id = ''app-client-id-from-oauth-provider'' config.app_secret
-  = ''app-client-secret-from-oauth-provider'' end ```  #### Setup 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 ```  ## Contributing  1. Fork it 2. Create your
+  tested path is Rails with Devise.  ## Installation  **NOTE: `v0.6.0` has been updated
+  for use with Rails 5.1 and requires Ruby 2.2 or greater.**  Add this line to your
+  application''s Gemfile:  ```ruby gem ''wcc-auth'', ''~> 0.3.2'' ```  If you are
+  using a Rails app with Devise you can use a special require hook that will setup
+  all the Devise specific configuration for you.  ```ruby gem ''wcc-auth'', ''~> 0.3.2'',
+  require: ''wcc/auth/devise'' ```  ## Configuration  There are a few steps to setup
+  your app. These instructions are specific to a Rails app.  #### Add the configuration
+  block to an initializer  In order to configure the gem you must run the `WCC::Auth.setup`
+  block. See below for an example:  ```ruby WCC::Auth.setup do |config| config.app_name
+  = "app-name" config.environment = Rails.env config.app_id = ''app-client-id-from-oauth-provider''
+  config.app_secret = ''app-client-secret-from-oauth-provider'' end ```  #### Setup
+  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'