DotNetOpenAuth v3.2 just came off the presses.  Lots of feature work and a few interop fixes in this release.  The biggest highlights being:

  • Very simple story for both RPs and OPs interested in interoperating with others whether they use sreg or one of the several AX formats (finally!)
  • OAuth 1.0a support
  • PPID generation for OPs to protect customers’ privacy.

Go download it.

As usual, see our VersionChanges wiki page for a more complete list of the work done for v3.2.  (There are lots more noteworthy changes that I don’t describe above).

9 thoughts on “DotNetOpenAuth v3.2 is done”
  1. Hello,
    As DotNetOpenAuth is not compatible with .Net 4.0 I tried to manage it to work with .Net 4.0 through code modification. I was able to make it work. However I have an issue with Partial Trust on .Net 4.0
    The issue with request for SecurityPermission being failed. It works with Full Trust, but not with High or Medium trust.
    I need to contact you if you could help me in this. my web site

  2. Hi Andrew,
    Just wanted to know if dotNetOpenID does/capable of what OpenID Membership Provider does. Just wanted to know the similarities and/or differences as both use Janrain's C# port

  3. robertocinq,

    As I recall the OpenID Membership Provider was built around an earlier version of DotNetOpenId, so with some work to use the latest version of this library, I think it would work — abismally. Actually I think using the ASP.NET Membership Provider system for OpenID is a bad idea all around since the membership provider interfaces were designed around username+password, and didn't count on redirects being required. It turns out this isn't a big deal to avoid altogether though.

    Similar questions answered on StackOverflow

  4. Hi,
    I had implemented OpenID to my application by reading your article and using dll "DotNetOpenId.dll" version "". I am able to sign in on my local machine using google,yahoo openids.But when I want to application hosted on server then i am redirected to google or yahoo but after redirect to my site AuthenticationStatus value is failed and it says "login failed". I know it is not related to this article but i am unable to find that article on your blog whihc I had read earlier.Can you help me


  5. Ulfat,

    I suggest you use a newer version of DotNetOpenAuth. But either way, there are other properties (like Exception) on the IAuthenticationResponse object that can give more detail. Turning on log4net logging will also give valuable detail.

Comments are closed.