AX not working with myopenid.com - hook to add/modify the AX elements is needed

http://openid.net/pipermail/general/2008-February/004029.html
I'm not sure what to do.

What is the "official" schema for the attribute exchange?
I notice that www.axschema.org defines several attributes; but they don't
work on myopenid.com.

And axschema is the official, it is stated at the linked thread.

The one we utilize in the mappings was the one that worked i believe axschema.org Openid.net seemed to have implemented their own slightly different i had that problem in the begining with it hence i put the schema their way because all the others supported it.

I think one of the readmes has something on that in it

I'm having a similar problem when trying to get both MyOpenID and Google OpenIDs to work. The problem isn't so much the schema URL (e.g. Google seems to work with both, so I just use the schema.net one to make MyOpenID play nicely), but rather the fact that the requested AX namespace is not handled consistently between providers. For instance, if I say in my request I want to use the ext1 namespace then Google will give me field names like this:

openid.ext1.value.country.1

while MyOpenID

insists on giving me its own 'ax' namespace no matter what:

openid.ax.value.country.1

Anybody else seen this?

I have a hack in openid_client_ax.module to work around this when retrieving AX values, but I was wondering if there's something I'm missing in the original request, or the OpenID Client AX configuration or something?

gthorisson,

According to the attribute exchange spec, the party composing the message gets to choose the namespace. So you can use "ax" or "ext1" as your namespace, but when the OpenID Provider composes the response, they are free to use whatever namespace they want, which may or may not be the same namespace you used in your request.

So when parsing the response, you need to search for the namespace defined as "http://openid.net/srv/ax/1.0".

As alex_b wrote alter hook is maybe not necessary - I went this way without any knowledge about this thread.

I introduced new hook "openid_ax_schema" which allows other AX extensions to inject theirs schema.

Going this way there is little problem with the "identifier", I solved this with using "identifiers" starting from 200. Using alter hook seems to be better, since you can check the max identifier and use dynamical identifier in the extension. But using dynamical identifiers is a bad idea, because after some change on the site - module update, installing some other AX entension - identifiers could change.

New patch introducing new hooks hook_openid_client_ax_schema and hook_openid_client_ax_schema_alter.

This is surely not a bad idea. Committed and pushed.