Model-Glue ActionPack:  OpenID Support

Description
-------------------------------------------------------------------------------
This actionpack provides an easy method for OpenID.  If you have any questions
about OpenID, check out http://www.openid.org to answer them before delving in.
With this plugin you'll be able to require users to login with their openid
and when they are properly authenticated with their openid server it will
redirect them to an event of your choice with all the information their openid
server sent back. There's an optional deniedEvent which the user will be
sent to in the event their server doesn't validate them. For additional updates
view the post on http://www.adamfortuna.com
(adam.fortuna AT gmail.com).


Requirements
-------------------------------------------------------------------------------
No other ActionPacks are required for this to run.   


Installation
-------------------------------------------------------------------------------
To use this ActionPack in a Model-Glue:Unity application, you need to do two
things:

1. This actionpack assums it's in /ModelGlue/actionpacks/config

2.  Copy the contents of config/Beans.xml into your application's ColdSpring.xml
file, then edit the various values to match your configuration.  They're all
documented in there.

3.  Add the following at the top of your application's ModelGlue.xml file, just
after the <modelglue> tag:

<include template="/ModelGlue/actionpacks/openid/config/ModelGlue.xml" />

4. Create an event in your dsp that forwards to openid such as: 
	<result do="openid.login" redirect="true" />
   This event can be completely overwritten, as the only thing you really need
   for it to work is an event that broadcasts "openidVerify".

That's it! 



Use
-------------------------------------------------------------------------------
This ActionPack adds a structure to the viewstate with two keys - identity and data.

Identity is the url the user entered (prefixed with http:// if it wasn't). 

Data is a structure of all information from the openid provider. The structure key
is the field that corresponds to the coldspring required/optional properties, so there
might be an email, dob, fullname key, etc. You shouldn't counton all any of the fields
set in coldspring to be returned in here.

Under the default installation, you can add events such as these for login, approved and denied events.

<!-- Login form, submits back to itself -->
		<event-handler name="openid.login">
			<broadcasts>
				<message name="openidVerify"/>
			</broadcasts>
			<views>
				<include name="body" template="dspLogin.cfm">
					<value name="xe.submit" value="openid.login" />
				</include>
			</views>
			<results>
				<result do="view.template" />
			</results>
		</event-handler>
		
		<!-- Called upon a successful server lookup. -->
		<event-handler name="openid.approved">
			<broadcasts />
			<views>
				<include name="body" template="dspLoginApproved.cfm" />
			</views>
			<results>
				<result do="view.template" />
			</results>
		</event-handler>
		
		<!-- Called upon a failed server lookup. -->
		<event-handler name="openid.denied">
			<broadcasts />
			<views>
				<include name="body" template="dspLoginDenied.cfm" />
			</views>
			<results>
				<result do="view.template" />
			</results>
		</event-handler>
		
There is a sample of these three files in the install directory as well. These files
are not actually used, because we wouldn't want to open up new events to a user if they're
not using them, so you have to do that yourself for now. :) The plugin it virtually
non-existant as far as what's needed, and the login form is the most complicated part.