Hey folks,<div><br></div><div>I've finally got some time to make the UX offered by <a href="http://openidux.dotnetopenauth.net/">http://openidux.dotnetopenauth.net/</a> available to other libraries besides DotNetOpenAuth. I'm planning on having the regular DNOA build spit out a .zip file of all the client resources necessary for that UX, but it will depend on the server-side maintaining a few "contracts" as outlined below. If anyone is familiar enough with their favorite OpenID library to feel confident making these changes and has the desire to do so, please contact me so we can get this done. </div>
<div><br></div><div>The three contracts are:</div><div><ol><li>An HTTP GET url that receives an OpenID identifier and returns a JSON-serialized object containing the immediate and setup auth requests for that identifier.</li>
<li>An HTTP GET/POST url that receives the positive assertion from the OP but instead of processing the assertion it merely renders javascript to forward the assertion to a parent window/frame.</li><li>An HTTP POST url that receives the user-selected positive assertion from the main window, verifies it, and actually logs the user in.</li>
</ol><div>It's pretty simple stuff. There are some specific details on #1 regarding extra parameters to include in the auth requests so that the AJAX client can track its own auth progress, but it's not too tough.</div>
<div><br></div><div>I hope there are some interested devs out there that can help out.</div><div><br></div>--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
</div>