wcc-auth 0.3.3 → 0.3.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 4cfc9a743cd01659828c3d7dc055c27538f67f53
-  data.tar.gz: 845b87ff6ac537b3d98d28a5b08899f255801d11
+  metadata.gz: f10f1aef9cdf3ee3030f9773876053391acf537a
+  data.tar.gz: d1aa25a309e9648a8832f2a2042675de54a9976f
 SHA512:
-  metadata.gz: 316f009800967d2af42cbcfc4a230739d7a515210f9e4551a1c09000319237571db01cffa70a7fc507d712fec96b774501acf760ab5dfead5e7ed1a341e1bd55
-  data.tar.gz: 280785fdcf6473be2aa73343885735babee8997603ad44e923bb114e7c0a36a7c0228221c2e94ab87cb4c032fbd835eb970a410e920948ea27f1b9d25f6bec02
+  metadata.gz: 83803f397bcb1f3d2714941f0a8e2ce085e7ca8f2eb699e0c64f801b63f05bbafcd56a42b77840fc2a74c1879215efb6c53f98849b403f418e28d5d3ef2cbce2
+  data.tar.gz: b0c2f79d95e663256c6387d1711efd6a0d85a6076abe57b5e5dd09e4490ebf93d84c581edfbec4318b9ad28164db1a4af70a400359345f62cb1108c620d6c880

data/lib/wcc/auth/config.rb

@@ -33,6 +33,12 @@ WCC::Auth::Config = Struct.new(:environment,
     self[:app_domain_suffix] || default_app_domain_suffix
   end
 
+  def url_for(app_name)
+    return ENV["#{app_name.to_s.upcase}_URL"] if ENV["#{app_name.to_s.upcase}_URL"]
+
+    "#{app_url_protocol_for(environment)}://#{app_name}#{app_domain_suffix_for(environment)}"
+  end
+
   def nucleus_url
     return ENV['NUCLEUS_URL'] if ENV['NUCLEUS_URL']
 
@@ -46,13 +52,18 @@ WCC::Auth::Config = Struct.new(:environment,
     end
   end
 
-  private
-
-  def default_app_url
-    "#{app_url_protocol}://#{app_name}#{app_domain_suffix}"
+  def app_domain_suffix_for(environment)
+    case environment.to_sym
+    when :production
+      ".watermark.org"
+    when :staging
+      ".staging.watermark.org"
+    when :development
+      ".dev"
+    end
   end
 
-  def default_app_url_protocol
+  def app_url_protocol_for(environment)
     case environment.to_sym
     when :production
       "https"
@@ -61,15 +72,18 @@ WCC::Auth::Config = Struct.new(:environment,
     end
   end
 
+  private
+
+  def default_app_url
+    "#{app_url_protocol}://#{app_name}#{app_domain_suffix}"
+  end
+
+  def default_app_url_protocol
+    app_url_protocol_for(environment)
+  end
+
   def default_app_domain_suffix
-    case environment.to_sym
-    when :production
-      ".watermark.org"
-    when :staging
-      ".staging.watermark.org"
-    when :development
-      ".dev"
-    end
+    app_domain_suffix_for(environment)
   end
 
   def default_authorize_site

data/lib/wcc/auth/version.rb

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

data/spec/spec_helper.rb

@@ -3,7 +3,6 @@ $LOAD_PATH.unshift(File.join(__FILE__, "..", "..", "lib"))
 require 'wcc/auth'
 
 RSpec.configure do |config|
-  config.treat_symbols_as_metadata_keys_with_true_values = true
   config.run_all_when_everything_filtered = true
   config.filter_run :focus
 

data/spec/wcc/auth/access_level_spec.rb

@@ -33,7 +33,7 @@ describe WCC::Auth::AccessLevel do
     it "returns array of records as listed in db argument" do
       levels = subject.all(test_db)
       expect(levels.count).to eq(2)
-      expect(levels.all? { |level| level.kind_of?(klass) }).to be_true
+      expect(levels.all? { |level| level.kind_of?(klass) }).to be_truthy
     end
 
     it "returns objects in level order" do
@@ -55,9 +55,9 @@ describe WCC::Auth::AccessLevel do
       b = klass.new
       a.level = 1
       b.level = 2
-      expect(a < b).to be_true
-      expect(b == a).to be_false
-      expect(b < a).to be_false
+      expect(a < b).to be_truthy
+      expect(b == a).to be_falsey
+      expect(b < a).to be_falsey
     end
   end
 

data/wcc-auth.gemspec

@@ -25,5 +25,5 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency "bundler", "~> 1.3"
   spec.add_development_dependency "rake"
-  spec.add_development_dependency "rspec"
+  spec.add_development_dependency "rspec", "~> 3.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: wcc-auth
 version: !ruby/object:Gem::Version
-  version: 0.3.3
+  version: 0.3.4
 platform: ruby
 authors:
 - Travis Petticrew
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-04-09 00:00:00.000000000 Z
+date: 2015-11-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cancancan
@@ -98,16 +98,16 @@ dependencies:
   name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '3.3'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '3.3'
 description: Authentication / Authorization library for Watermark apps
 email:
 - tpetticrew@watermark.org
@@ -161,44 +161,43 @@ rubyforge_project:
 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.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'
+  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 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"
+  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
+  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