OpenID AX/SREG step 1 of road map completed

With Drupal core OpenID module, users can authenticate on your Drupal  
site with
OpenID. With the OpenID extensions AX and SReg it is also possible to  
exchange
with user profile data. Alex Barth, Darren Ferguson and I have worked  
in the
past months together to improve the existing OpenID AX / SREG modules:

OpenID AX/SREG client support

• OpenID Client AX  
  (API module)
• OpenID Client SReg  
  (API module)

OpenID AX/SREG provider support

• OpenID Provider -  
  support for Drupal as OpenID provider
• OpenID Provider AX  
  (API module)
• OpenID  
  Provider SReg (API module)
• OpenID  
  Provider Persona (OpenID profiles, alternative to content profile)

OpenID AX/SREG client + provider

• OpenID CP Field -  
  integration with content profile

In  most of the cases, you really don't need to know much of all of  
these
modules. Here is a quick start guide for getting started with SReg and  
Attribute Exchange on Drupal.

Quick start guide for using OpenID Attribute Exchange

Goal: exchange user profiles between Drupal sites.

Relying Party (RP) site

This is the site where the user wants to log into with the identitiy  
from the OpenID Provider (OP).

1) Install OpenID Client AX

OpenID Provider (RP) site

This is the site where the user's OpenID identity and attributes are  
being hosted.

1) Install OpenID Provider  
AX, OpenID Provider

Common steps, both for RP and OP sites

2) Install OpenID CP Field  
on both sites.
3) Configure Content Profile, add desired CCK fields for your user  
profiles.
4) Go to admin/content/node-type/[profiletype]/cp-field and set up  
exactly the
same mapping for each CCK field that you would like to transmit. It is  
recommendable to map
suitable OpenID AX attributes to your profiles fields but what
matters is that the mappings between the two sites match.
5) Ready!

Now create a user with a content profile node at the OP site and then  
use this user's OpenID to log in in to the RP site. The profile will  
be created on the fly.

Work accomplished with Step 1 of OpenID roadmap

• Unified configuration of field mappings between RP and OP.
• Reduced function of Openid client/provider sreg/ax modules to API  
  modules.
• Improved mapping UI of openid_cp_field and made it exportable.

For more information about the set up, please refer to the project  
pages and the README.txt of the projects.