Empact-authlogic_rpx 1.1.2 → 1.1.3

data/Empact-authlogic_rpx.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{Empact-authlogic_rpx}
-  s.version = "1.1.2"
+  s.version = "1.1.3"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Paul Gallagher / tardate"]
-  s.date = %q{2010-02-25}
+  s.date = %q{2010-02-26}
   s.description = %q{Authlogic extension/plugin that provides RPX (rpxnow.com) authentication support}
   s.email = %q{gallagher.paul@gmail.com}
   s.extra_rdoc_files = [

data/README.rdoc

@@ -1,5 +1,10 @@
 = Authlogic_RPX
 
+== Changes
+
+This fork enables full-featured auto-registration without sacrificing database constraints.
+{See the source for the sample workflow}[http://github.com/Empact/rails-authlogic-rpx-sample/].
+
 == Purpose
 
 Authlogic_RPX is an Authlogic extension library that provides support for authentication using the RPX multi-authentication service offered by JanRain. To use RPX, you must first register your application at {RPX}[http://rpxnow.com/]. A free "Basic" account is available, in addition to paid enhanced versions. All work with Authlogic_RPX.  
@@ -158,9 +163,6 @@ The user_model parameter specifies the name of the user/member model in your app
 You may need to customise the migration file to remove database constraints on other fields if they will be unused in the RPX case
 (e.g. crypted_password and password_salt to make password authentication optional).
 
-If you are using auto-registration, you must also remove any database constraints for fields that will be automatically mapped
-(see notes in "3. Add custom user profile mapping during auto-registration")
-
 ==== Sample Migration Generated Script (using internal mapping)
 
 The following command will generate a migration for the case where you want to use authlogic_rpx internal mapping and your user model is called 'User':
@@ -182,8 +184,6 @@ The migration script will appear like this:
       
       # == Customisation may be required here ==
       # You may need to remove database constraints on other fields if they will be unused in the RPX case
-      # (e.g. crypted_password and password_salt to make password authentication optional). 
-      # If you are using auto-registration, you must also remove any database constraints for fields that will be automatically mapped
       # e.g.:
       #change_column :users, :crypted_password, :string, :default => nil, :null => true
       #change_column :users, :password_salt, :string, :default => nil, :null => true
@@ -357,22 +357,10 @@ If you have other fields you want to map, you can provide your own implementatio
   end
 
 
-WARNING: if you are using auto-registration, any fields you map should NOT have constraints enforced at the database level.
-Authlogic_rpx will optimistically attempt to save the user record during registration, and violating a database constraint will cause the authentication/registration to fail.
-
-You can/should enforce any required validations at the model level e.g.
+WARNING: if you are using auto-registration, you will need to implement a special workflow which allows
+users to address validation errors at registration time.
 
-  validates_uniqueness_of   :username, :case_sensitive => false
-  
-This will allow the auto-registration to proceed, and the user can be given a chance to rectify the validation errors on your user profile page.
-
-If it is not acceptable in your application to have user records created with potential validation errors in auto-populated fields, you will need to override map_rpx_data and implement whatever special handling makes sense in your case. For example:
-  
-* directly check for uniqueness and other validation requirements
-* automatically "uniquify" certain fields like username
-* save conflicting profile information to "pending user review" columns or a seperate table
-
-{See the source for the sample user_session.rb}[http://github.com/tardate/rails-authlogic-rpx-sample/blob/master/app/models/user_session.rb].
+{See the source for the sample workflow}[http://github.com/Empact/rails-authlogic-rpx-sample/].
 
 ==== 3b. map_rpx_data_each_login: user profile mapping during login
 

data/VERSION

@@ -1 +1 @@
-1.1.2
+1.1.3

data/lib/authlogic_rpx.rb

@@ -1,3 +1,4 @@
+require 'authlogic'
 require "authlogic_rpx/version"
 require "authlogic_rpx/acts_as_authentic"
 require "authlogic_rpx/session"

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 1
   - 1
-  - 2
-  version: 1.1.2
+  - 3
+  version: 1.1.3
 platform: ruby
 authors: 
 - Paul Gallagher / tardate
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-02-25 00:00:00 -05:00
+date: 2010-02-26 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency