DotNetOpenId 2.1.0 released, adds Attribute Exchange support

DotNetOpenId had a double release tonight.  Version 2.0.1 is a maintenance release with a few minor bug fixes.  Version 2.1 adds built-in support for the Attribute Exchange extension, but introduces a couple of small breaking changes.  Check out the VersionChanges page to decide which version is right for you.

Download the new versions here.

This Post Has 3 Comments

  1. Hi Andrew,

    First of all, let me say thanks for the all work you and the rest of the team has done in bringing OpenID support to .NET.

    I was delighted to see that you have included Attribute Exchange support in this latest release. I am on of those people who exhibits a lukewarm attitude toward OpenID – until you mention Attribute Exchange. This extension greatly expands the utility of OpenID in my view.

    To be honest, in the absence of documentation, I personally find it difficult to figure out how to use the library effectively and quickly. I haven’t yet hit upon a method of scanning the samples/source in such a way that the use of the library is made clear to me.

    I know your plate is full, but are you able to give a quick overview of how to initiate an Attribute Exchange? Specifically, I want to:
    1) Operate an OpenID portal that supports custom attributes
    2) As a relying party, request/fetch said custom attributes from the portal

    Right now, I am simply trying to demonstrate attribute exchanging for myself, but I am having little luck. I find I can programmatically initiate a request easily (OpenIDRelyingParty.CreateRequest) and I can see the simple registration object returned in the IncomingExtensions of the response, but that is the extent of it. I am unsure how to ‘use’ the Attribute Exchange extension.

    Any direction you can provide in this regard is greatly appreciated.

  2. You’re absolutely right, jfp. I keep feeling like the documentation is adequate because the unit tests show how simple it is… but I forget that most people don’t download the unit tests nor do they want to wade through them to find that “easy” one-word access to what they want. I’ll post on how to use AX shortly to help you and everyone else out.
    Thanks for your comment!

Comments are closed.