wcc-auth 0.3.2 → 0.3.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b1e50254917d5510fdf6c8faafe55212618eec83
-  data.tar.gz: c36503c98bdf1a2bfdfc3f71e91ca05082f6dee9
+  metadata.gz: 4cfc9a743cd01659828c3d7dc055c27538f67f53
+  data.tar.gz: 845b87ff6ac537b3d98d28a5b08899f255801d11
 SHA512:
-  metadata.gz: 84de7ee3f83e943439303e7b5991140eddf211e49d11ede4bb4207d6b7824e7b01891a32b167908729e44a9e96a205588337cf0e0b4e8e5976e253977a22a715
-  data.tar.gz: f0a58d742eadef87c1bd77cb8701759dda8bac0ae5c418c5fe7a46db54d24fe3e2d94f955def564c259b260831fd1dbc5ba171db48c81b8d6905a45bd3b09c35
+  metadata.gz: 316f009800967d2af42cbcfc4a230739d7a515210f9e4551a1c09000319237571db01cffa70a7fc507d712fec96b774501acf760ab5dfead5e7ed1a341e1bd55
+  data.tar.gz: 280785fdcf6473be2aa73343885735babee8997603ad44e923bb114e7c0a36a7c0228221c2e94ab87cb4c032fbd835eb970a410e920948ea27f1b9d25f6bec02

data/README.md

@@ -11,14 +11,14 @@ any Ruby project. Currently, the only tested path is Rails with Devise.
 Add this line to your application's Gemfile:
 
 ```ruby
-gem 'wcc-auth', '~> 0.3.0'
+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.0', require: 'wcc/auth/devise'
+gem 'wcc-auth', '~> 0.3.2', require: 'wcc/auth/devise'
 ```
 
 ## Configuration
@@ -54,6 +54,7 @@ end
 ```ruby
 class User < ActiveRecord::Base
   include WCC::Auth::Providers::ActiveRecord
+  devise :omniauthable
 
   # ...
 

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"],
+      applications: raw_info["applications"]
     }
   end
 

data/lib/wcc/auth/access_level.rb

@@ -17,10 +17,10 @@ module WCC::Auth
     end
 
     def self.[](index_or_slug, db=ACCESS_LEVELS)
-      all(db).select do |al|
+      all(db).find do |al|
         al.level.to_s === index_or_slug.to_s ||
           al.slug === index_or_slug.to_s
-      end.last
+      end
     end
 
     def self.all(db=ACCESS_LEVELS)

data/lib/wcc/auth/version.rb

@@ -1,5 +1,5 @@
 module WCC
   module Auth
-    VERSION = "0.3.2"
+    VERSION = "0.3.3"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: wcc-auth
 version: !ruby/object:Gem::Version
-  version: 0.3.2
+  version: 0.3.3
 platform: ruby
 authors:
 - Travis Petticrew
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-09-11 00:00:00.000000000 Z
+date: 2015-04-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cancancan
@@ -158,45 +158,47 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.4.2
 signing_key: 
 specification_version: 4
-summary: '# WCC::Auth  Provides the necessary tools for handling authentication through
-  Watermark''s OAuth provider as well as authorizing the user has access to specific
+summary: "# WCC::Auth  Provides the necessary tools for handling authentication through
+  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.0'' ```  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.0'', require: ''wcc/auth/devise''
+  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  # ...  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`
+  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
+  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 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'
+  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 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