Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • It would be helpful if you would include, on this question, what the actual problem is. As you didn't find the other question helpful, others will not find this one helpful either, and people will have a hard time answering your question... Commented Jan 29, 2010 at 22:38
  • @Rick: OK, I tried to clarify with some edits. Commented Jan 29, 2010 at 22:46
  • Please include the logs. :) dotnetopenauth.net/developers/code-snippets/… Commented Jan 30, 2010 at 2:19
  • These logs don't show the problem. They show just one check_authentication message, which comes back positive. Can you include more of the log? Also, the parts of it that you're scrubbing actually will likely be useful -- and they don't actually expose any security-compromising details. Signatures... nonces... these aren't secrets. They're assurances that messages haven't changed. Commented Feb 2, 2010 at 5:12
  • 1
    My suggestion (as clearly outlined in the link I provided) was to set a config entry to 0:10 - and you have it set as 0:05. Commented Feb 10, 2010 at 10:44