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.

2
  • You were right - I was using separate OpenIdRelyingParty instances to initiate and complete the login process, and one of them was not passing null in the constructor. I was operating under the assumption that a class that implements IDisposable should be disposed, so it's good to hear that it's safe to instantiate one static instance. I was using stateless because I was planning for a load-balanced environment - would you recommend implementing an IRelyingPartyApplicationStore in order to achieve safety from attacks with AOL and other OpenID 1.1 providers? Commented Feb 2, 2010 at 15:34
  • I always recommend a state store if you can implement it. Otherwise, I'd leave OpenID 1.1 OP support at its stateless default of off. AOL ought to be about done with their 2.0 OP launch pretty soon here anyway. Commented Feb 3, 2010 at 0:01