invitational 1.1.5 → 1.1.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 17a5a124a390f4503a9ee874522e80f511c03664
-  data.tar.gz: fc524576ad2faf67f5d8fa8d3901c0211a38d09d
+  metadata.gz: e6be26e6c2ba8c14eedc3c84029c42fb2d8ba27c
+  data.tar.gz: adfd381d2d9b1484211b2dd56e153eda3f806990
 SHA512:
-  metadata.gz: 67ebd517377d4256a47063e18f97739b94d74f9b73061b4c0a5a7abd41e0709b00da020fec4ca15c4bdcbd53b3150b6736c3daa20f8803a878f7f7414cd12b3a
-  data.tar.gz: 6a8a893f60048c60d765c08e1ddcc60b6cd2673d6e1cab718a0baa889cd5a5165fc254ba9343fe6dd97335b296cdcf30d6cd44b557a37e3f81b6ea43ad7f59e0
+  metadata.gz: 2b893c783473e121a31c412639316039b8e8aec19b508b7a660949f0ccefea5e245939d0d7872c11aefa9d322a55c22d14a68560624347e6a323db3f126ccd23
+  data.tar.gz: fa83149b377ba8788bee298f644346e8f1363def5b3c63ccb9f8bf3d2ce9bdf0709c9996c748c7ef05864e0e1cba4a18dc1606716fc8507ca2d0afacfea7b78e

data/README.md

@@ -1,6 +1,8 @@
+[![Gem Version](https://badge.fury.io/rb/invitational.png)](http://badge.fury.io/rb/invitational)
+
 #Overview
 
-The purpose of Invitational is to eliminate the tight coupling between user identity/authentication and application authorization.  It is a common pattern in multi-user systems that in order to grant access to someone else, an existing administrator must create a user account, providing a username and password, and then grant permissions to that account.  The administrator then needs to communicate the username and password to the individual, often via email.  The complexity of this process is compounded in multi-account based systems where a single user might wind up with mutiple user accounts with various usernames and passwords.
+The purpose of Invitational is to eliminate the tight coupling between user identity/authentication and application functional authorization.  It is a common pattern in multi-user systems that in order to grant access to someone else, an existing administrator must create a user account, providing a username and password, and then grant permissions to that account.  The administrator then needs to communicate the username and password to the individual, often via email.  The complexity of this process is compounded in multi-account based systems where a single user might wind up with mutiple user accounts with various usernames and passwords.
 
 Inspired by 37Signals' single sign-on process for Basecamp, Invitational provides an intermediate layer between an identity model (i.e. User) and some entity to which authorization is given.  This intermediate layer, an Invitation, represents a granted role for a given entity.  These roles can then be leveraged by the application's functional authorization system.
 

data/lib/generators/invitational/install/install_generator.rb

@@ -17,6 +17,10 @@ module Invitational
         template "invitation.rb", "app/models/invitation.rb"
       end
 
+      def add_to_gemfile
+        gem "cancancan"
+      end
+
       def ability_model
         @identity_model = @identity_class.underscore
         template "ability.rb", "app/models/ability.rb"

data/lib/invitational/version.rb

@@ -1,3 +1,3 @@
 module Invitational
-  VERSION = "1.1.5"
+  VERSION = "1.1.6"
 end

data/lib/tasks/invitational_tasks.rake

@@ -3,8 +3,7 @@ namespace :invitational do
   task :create_uberadmin => [:environment] do
     email = Digest::SHA1.hexdigest(DateTime.now.to_s) + "@localhost"
 
-    creator = Invitational::CreatesUberAdminInvitation.for email
-    invitation = creator.invitation
+    invitation = Invitation.invite_uberadmin email
 
     puts "Your uberadmin invitation claim hash is: #{invitation.claim_hash}"
     puts "Visit your claim URL with this hash to claim the invitation."

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: invitational
 version: !ruby/object:Gem::Version
-  version: 1.1.5
+  version: 1.1.6
 platform: ruby
 authors:
 - Dave Goerlich
@@ -123,7 +123,8 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 2.3.0
-description: See summary
+description: Solution that eliminates the tight coupling between user identity/authentication
+  and application functional authorization
 email:
 - dave@d-i.co
 - joe@d-i.co
@@ -183,5 +184,6 @@ rubyforge_project:
 rubygems_version: 2.2.0
 signing_key: 
 specification_version: 4
-summary: Manage users and the objects they belong to
+summary: Solution that eliminates the tight coupling between user identity/authentication
+  and application functional authorization
 test_files: []