Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

After having created a custom SSO system for my company, I decided to take it for a spin and see how compliant it is. The interop testing at for attribute exchange passed, so I then tried to create a new SO account with it.

The account was created successfully, the name was set properly but the email address didn't get used (it didn't show up on my profile page).

When SO makes the checkid_setup call, it asks for both name and email (using both axschema and schema.openid types):

[ns.alias3] =>
[alias3.if_available] => alias1,alias2,alias3,alias4
[alias3.mode] => fetch_request
[alias3.type.alias1] =>
[alias3.count.alias1] => 1
[alias3.type.alias2] =>
[alias3.count.alias2] => 1
[alias3.type.alias3] =>
[alias3.count.alias3] => 1
[alias3.type.alias4] =>
[alias3.count.alias4] => 1

In response to that request my server sends the following back:

[] =>
[ax.mode] => fetch_response
[ax.type.alias1] =>
[ax.count.alias1] => 1
[ax.value.alias1.1] => Jack
[ax.type.alias2] =>
[ax.count.alias2] => 1
[ax.value.alias2.1] =>

My server chooses to recognize only the openid types, so the axschema types are omitted from the response. All above fields are signed and I'm pretty sure the email address has not been used before to create an SO account.

My question is: based on the above, is there anything that should be done in another way?

share|improve this question
I experience this same problem, the following attributes are requested and my provider responds with values for each, but all are ignored AFAICT: * * * * – user916968 Dec 3 '12 at 12:49

You must log in to answer this question.

Browse other questions tagged .