+1
We currently have a case where we do not support identity-less OpenID
transactions. It would be nice to be able to respond with a code that
implies "Not supported".
Thanks,
George
On 1/13/10 1:20 PM, Allen Tom wrote:
I believe that RPs in general will not be able to automatically
recover from errors (other than to tell the user that something bad
happened), so any error that's returned will need to be manually
interpreted by the RP's developer.
I would like to to see errors returned using standard error codes
(machine readable) along with an URL or string for the owner of the RP
to manually troubleshoot the problem. The string/url should not be
displayed to the end user. This sounds like a very reasonable feature
to include in OpenID v.Next.
Allen
On 1/6/10 10:04 AM, "Breno de Medeiros" <[email protected]> wrote:
I think for developers it would be much more useful to have test
OPs that provide detailed error logs (e.g., entire exception stack
trace, which production OPs often do not provide), so RP
developers can use that for debugging.
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
_______________________________________________
specs mailing list
[email protected]
http://lists.openid.net/mailman/listinfo/openid-specs
