Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConsumerManager.verifyDiscovered1 is not giving enough details in VerificationResult._statusMsg #203

Open
GoogleCodeExporter opened this issue Jun 4, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

In relation to my previous reported problem #202,

when a problem like that happens, it's very difficult to get any meaningful 
diagnosis out of openid4java. The only error message we get is "Discovered 
information verification failed." and it does not go into the details of which 
aspect has failed.

In OpenID, relying party has no secret to hide from the person who's trying to 
authenticate. So as much diagnostic information should be given to the status 
message as possible, to diagnose configuration issues in the server/client, etc.

For example, in ConsumerManager.verifyDiscovered1, instead of reporting errors 
to the logger, those error messages should be primarily put into 
VerifiedResult._statusMsg, which is where it belongs.

In the "stateless mode / bare response verification" mode, the 
verifyDiscovered1 method should also report what openIDs it has discovered and 
why it rejected it when it fails to find a matching one.

It would have made a troubleshooting like issue #202 very easy. As it stands 
right now, it took us to attach a debugger and trace through the code to tell, 
which would have been completely impractical if this had happened at some 
remote site.

Original issue reported on code.google.com by [email protected] on 4 Dec 2013 at 4:02

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant