Support attribute exchange to retrieve user details

+1 These are the attributes supported by Yahoo as well http://developer.yahoo.net/blog/archives/2009/12/yahoo_openid_now_with_attribute_exchange.html

Is there a simple solution I can use in the meantime or is it a large patch?

I've attached a branch to this bug that implements the feature. It doesn't require any additional configuration over trunk, and should work with any provider that advertises support for the Attribute Exchange extension in its XRDS.

I've done some basic testing against Google and Yahoo (who support slightly different sets of attributes), but would appreciate reports from any one else willing to test it.

Fix merged in r66.

I've found that r66 prevents attributes from myopenid.com from being retrieved. It looks like the issue is with views.py.

I've attached a patch that should fix the problem. It enables attributes from myopenid.com to still be retrieved while still allowing attributes from Google to be retrieved as well. I have not tested this with any other OpenID providers.

I just grabbed the latest bzr release today as I was having an issue like one posted in the answers section about creating the accounts with the openiduser name instead of the actual user name. By the description, it sounded like this was corrected. However, I am still getting this as the account name but the user first and last name as well as the E-mail address are filled in correctly.
Am I missing something or is there still a bug on this?

I was testing against my Google account if that helps at all.

Hi,

The username will default to "openiduser" if it does not find a value for the "nickname" attribute. From auth.py:

nickname = details['nickname'] or 'openiduser'

Hope that helps,
Joe

Thanks for the response Joe.

It helps me to a point I guess. It explains what's happening.

I guess Google doesn't send the nickname at all as I seem to only get the E-mail address and the first and last name.

Is there any reason that the first and last names aren't used for the account name if the nickname field is empty?

Bjorn

I'm not sure of the reasoning behind defaulting to 'openiduser'. You could edit the auth.py file to change it to any combination of other attributes: first+last name, email, email substituting @ for ".", etc.

Thanks Joe, that put me on the right track.

I forgot to change the status of this bug when I submitted my patch. I believe the fix submitted in r66 opens up a new bug and therefore does not completely fix this problem.

I've filed bug 607553 to track the problems with myOpenID. They appear to have based their implementation on a superseded draft specification and used different attribute names than everyone else. I'll make sure the 0.3 release includes a work around.

As for the username issue, please file a new bug if you'd like to see the behaviour changed. Comments on closed bug reports are liable to be lost.