User is a members of site1.com and wants to login site2.com
use token to Authenticate the user to allow site1.com user to access web application on site2.com

Here's how it works
-From site2.com User clicks on "login to site2.com with site1.com account"
-site2.com redirects user to site1.com, (site2.com) sending site1.com the token method, application identifier, secretID (generated by site2.com), policyURL, acceptURL and rejectURL)
-User login to site1.com with his/her registered site1.com username and password
-Assuming the user has successfully logged in; site1.com displays site2.com application name along with site2.com policyURL hyperlink.
- User clicks "accept agreement" to proceed, otherwise clicks cancel and site1.com redirects the user to rejectURL on site2.com.
- site1.com generates new tokenkey for the user (if one has not been created).
- site1.com creates application identifier ID in the database table under the users memberID (if one does not exist for the application).
- site1.com stores this users tokenkey and secretID in site1.com database under application identifier ID table for the user.
- site1.com then redirect user to acceptURL on site2.com, returning to site2.com the users memberID and tokenkey.
- site2.com display to the user "verification successful" (optional)
- site2.com create a cookie for the user to allow the user future access to site2.com
- site2.com stores the user memberID, secretID, and tokenkey to site2.com database.
- User is now logged in

The next time the user wishes to login to site2.com, site2.com will authenticate the user on behalf. First site2.com application will check if there is a cookie for the user, if one exist site2.com application then calls the site1.com API function getToken. It checks this information if site1.com and site2.com token matches. In the case where cookie does not exist (user login from another computer) the user will need to login to site1.com site again (as above) this time it would not generate a new token but resend the user existing token for the application to site2.com, application at site2.com will then Authenticate the user and create a cookie for that user.