Empact-authlogic_rpx 1.1.2 → 1.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/Empact-authlogic_rpx.gemspec +2 -2
- data/README.rdoc +8 -20
- data/VERSION +1 -1
- data/lib/authlogic_rpx.rb +1 -0
- metadata +3 -3
@@ -5,11 +5,11 @@
|
|
5
5
|
|
6
6
|
Gem::Specification.new do |s|
|
7
7
|
s.name = %q{Empact-authlogic_rpx}
|
8
|
-
s.version = "1.1.
|
8
|
+
s.version = "1.1.3"
|
9
9
|
|
10
10
|
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
|
11
11
|
s.authors = ["Paul Gallagher / tardate"]
|
12
|
-
s.date = %q{2010-02-
|
12
|
+
s.date = %q{2010-02-26}
|
13
13
|
s.description = %q{Authlogic extension/plugin that provides RPX (rpxnow.com) authentication support}
|
14
14
|
s.email = %q{gallagher.paul@gmail.com}
|
15
15
|
s.extra_rdoc_files = [
|
data/README.rdoc
CHANGED
@@ -1,5 +1,10 @@
|
|
1
1
|
= Authlogic_RPX
|
2
2
|
|
3
|
+
== Changes
|
4
|
+
|
5
|
+
This fork enables full-featured auto-registration without sacrificing database constraints.
|
6
|
+
{See the source for the sample workflow}[http://github.com/Empact/rails-authlogic-rpx-sample/].
|
7
|
+
|
3
8
|
== Purpose
|
4
9
|
|
5
10
|
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
|
|
158
163
|
You may need to customise the migration file to remove database constraints on other fields if they will be unused in the RPX case
|
159
164
|
(e.g. crypted_password and password_salt to make password authentication optional).
|
160
165
|
|
161
|
-
If you are using auto-registration, you must also remove any database constraints for fields that will be automatically mapped
|
162
|
-
(see notes in "3. Add custom user profile mapping during auto-registration")
|
163
|
-
|
164
166
|
==== Sample Migration Generated Script (using internal mapping)
|
165
167
|
|
166
168
|
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:
|
|
182
184
|
|
183
185
|
# == Customisation may be required here ==
|
184
186
|
# You may need to remove database constraints on other fields if they will be unused in the RPX case
|
185
|
-
# (e.g. crypted_password and password_salt to make password authentication optional).
|
186
|
-
# If you are using auto-registration, you must also remove any database constraints for fields that will be automatically mapped
|
187
187
|
# e.g.:
|
188
188
|
#change_column :users, :crypted_password, :string, :default => nil, :null => true
|
189
189
|
#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
|
|
357
357
|
end
|
358
358
|
|
359
359
|
|
360
|
-
WARNING: if you are using auto-registration,
|
361
|
-
|
362
|
-
|
363
|
-
You can/should enforce any required validations at the model level e.g.
|
360
|
+
WARNING: if you are using auto-registration, you will need to implement a special workflow which allows
|
361
|
+
users to address validation errors at registration time.
|
364
362
|
|
365
|
-
|
366
|
-
|
367
|
-
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.
|
368
|
-
|
369
|
-
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:
|
370
|
-
|
371
|
-
* directly check for uniqueness and other validation requirements
|
372
|
-
* automatically "uniquify" certain fields like username
|
373
|
-
* save conflicting profile information to "pending user review" columns or a seperate table
|
374
|
-
|
375
|
-
{See the source for the sample user_session.rb}[http://github.com/tardate/rails-authlogic-rpx-sample/blob/master/app/models/user_session.rb].
|
363
|
+
{See the source for the sample workflow}[http://github.com/Empact/rails-authlogic-rpx-sample/].
|
376
364
|
|
377
365
|
==== 3b. map_rpx_data_each_login: user profile mapping during login
|
378
366
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
1.1.
|
1
|
+
1.1.3
|
data/lib/authlogic_rpx.rb
CHANGED
metadata
CHANGED
@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
|
|
5
5
|
segments:
|
6
6
|
- 1
|
7
7
|
- 1
|
8
|
-
-
|
9
|
-
version: 1.1.
|
8
|
+
- 3
|
9
|
+
version: 1.1.3
|
10
10
|
platform: ruby
|
11
11
|
authors:
|
12
12
|
- Paul Gallagher / tardate
|
@@ -14,7 +14,7 @@ autorequire:
|
|
14
14
|
bindir: bin
|
15
15
|
cert_chain: []
|
16
16
|
|
17
|
-
date: 2010-02-
|
17
|
+
date: 2010-02-26 00:00:00 -05:00
|
18
18
|
default_executable:
|
19
19
|
dependencies:
|
20
20
|
- !ruby/object:Gem::Dependency
|