? openid_cp_field_doc.patch
? ui_review.patch
Index: README
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/openid_cp_field/README,v
retrieving revision 1.2.2.2
diff -u -p -r1.2.2.2 README
--- README	31 Mar 2009 01:59:21 -0000	1.2.2.2
+++ README	21 Apr 2009 22:50:44 -0000
@@ -1,5 +1,66 @@
-OPENID CONTENT PROFILE FIELDS PERMISSIONS
------------------------------------------
-Module will sit between the openid_provider_persona module and the content permissions
-for content profile module. This will allow us to determine what we can return with the
-module
+; $Id$
+
+OpenID Content Profile Field
+----------------------------
+
+This module maps OpenID fields to Content Profile fields. It can be used for 
+OpenID clients and providers.
+
+OpenID Provider: A site that provides OpenID authentication.
+OpenID Client:   Also called "relying party" or "consumer". A site that a user 
+                 logs into using OpenID.
+OpenID fields:   A field according to the OpenID Simple Registration standard 
+                 or the OpenID Attribute Exchange Standard.
+ 
+OpenID Content Profile Field for OpenID Clients
+-----------------------------------------------
+
+Required modules:
+
+* OpenID (core module) - provides basic OpenID authentication for OpenID clients.
+* Content Profile - uses nodes for user profiles.
+
+  Either one or both of:
+
+* OpenID Client AX - implements OpenID Attribute Exchange.
+* OpenID Client SREG - implements OpenID Simple Registration.
+
+1) Install and configure the above modules.
+2) Activate Content Profile functionality for a content type.
+3) Edit the content type, go to OpenID mapping tab.
+4) Map OpenID fields to fields on your content type.
+
+After these mappings are defined, newly logged in users will have their profile 
+populated with fields form the OpenID provider.
+
+Limitations:
+
+* If user's OpenID provider does not expose the OpenID fields defined in the 
+  mapping, no profile will be created.
+* There is no synchronization: The content profile won't be updated if a user's
+  data changes on the OpenID provider.
+* For already existing users the profile is only created at the first login 
+  with the OpenID, not when adding the OpenID to their account.
+
+OpenID Content Profile Field for OpenID Providers
+-------------------------------------------------
+
+Required modules:
+
+* OpenID Provider - provides OpenID authentication to other sites.
+
+  Either one or both of:
+
+* OpenID Provider AX - implements OpenID Attribute Exchange provider side.
+* OpenID Provider SReg - implements OpenID Simple Registration provider side.
+
+  Either one of:
+
+* Content Profile - uses nodes for user profiles
+* OpenID Provider Persona - provides full implementation of OpenID Attribute 
+  Exchange fields and persona support.
+ 
+After you installed and configured the above modules, edit the Profile 
+content-type, go to OpenID field mapping tab and configure the mapping. When
+the OpenID provided by this site is being used, Drupal will expose OpenID AX
+and SReg fields according to the mapping.
\ No newline at end of file
Index: openid_cp_field.info
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/openid_cp_field/openid_cp_field.info,v
retrieving revision 1.1.2.3
diff -u -p -r1.1.2.3 openid_cp_field.info
--- openid_cp_field.info	18 Apr 2009 14:22:28 -0000	1.1.2.3
+++ openid_cp_field.info	21 Apr 2009 22:50:44 -0000
@@ -1,6 +1,6 @@
-; $Id: openid_cp_field.info,v 1.1.2.3 2009/04/18 14:22:28 darrenferguson Exp $
+; $Id: openid_cp_field.info,v 1.1.2.2 2009/03/31 01:59:21 darrenferguson Exp $
 name = OpenID Content Profile Field
-description = Provides the ability to determine whether we can return data for a particular content profile field
+description = Provides mapping user interface and logic between OpenID attributes and content profile node fields.
 version = "6.x"
 core = 6.x
 dependencies[] = content_profile