When I asked if you could share your single sign-on classes you said you were working on the documentation...
...well several months later, today in February 2011, this documentation must be the best ever written, as we appear to still be waiting on it, yes?
May we see what you have so far, especially the actual code, please?
(most PHP if well structured and well written needs comparatively little documentation...)
|2011-02-24 09:15:24 - In reply to message 1 from Monty Dog|
|I am glad you have reminded me because I practically forgot about it. The main issue is that it takes a lot of time to document it properly. Since I had more priority issues, I ended up forgetting.|
There is also the matter of providing proper examples that let you try it in your own applications.
Another aspect is that it does not yet provide a full OpenID 2.0 implementation. I know that at least the current implementation balks at Yahoo OpenID provider.
Another issue is that request URI may become too long and some browsers, apparently some mobile device browsers, may truncate URLs. I know that Google OpenID provider balks long URIs and halt the process.
So, basically the current OpenID client and provider implementation work together, despite the eventual URL truncation, but I am not sure if this is still useful for you.
What exactly did you intend to use this?
Do you want to use the OpenID client to authenticate with foreign providers?
Do you want to have your owner OpenID provider for foreign clients?
Or you just want to have your own client working with your own provider like PHPClasses/JSClasses uses Icontem Accounts?