问题描述
我的网站将使用唯一的OpenID进行身份验证。我想拉用户详细信息通过属性交换了下来，但属性交换似乎造成了很多痛苦的计算器。
My website will be using only OpenID for authentication. I'd like to pull user details down via attribute exchange, but attribute exchange seems to have caused a lot of grief for StackOverflow.
什么是发挥在行业当前的状态？是否有任何OpenID提供商做属性交换的一份体面的工作？
What is the current state of play in the industry? Does any OpenID provider do a decent job of attribute exchange?
我是不是应该避开远离OpenID属性交换干脆？
Should I just steer away from OpenID attribute exchange altogether?
该如何处理的功能不一致的支持？
How can I deal with inconsistent support for functionality?
推荐答案
下面对堆栈溢出，我们只是使用的扩展现在，因为有一些问题与属性交换（AX）。
Here on Stack Overflow, we're just using the Simple Registration extension for now, as there were some issues with Attribute Exchange (AX).
最大是的OpenID提供（OP）不同意在其来使用。对于AX最终确定的规范说属性的URL应该来自然而，一些有机磷农药，尤其是我们的最喜欢的，识别的 。我不会让一个列表，其中的那些太淘气了，哪些是好的！
The biggest was OpenID Providers (OP) not agreeing on which attribute type urls to use. The finalized spec for AX says that attribute urls should come from http://www.axschema.org/ However, some OPs, especially our favorite http://myopenid.com, recognize other urls. I wasn't going to keep a list of which ones were naughty and which were nice!
另一个问题是，大多数我试图在与AX查询只是没有返回信息的有机磷农药的 - 我可能是做错了什么（情况屡有:)），但我已经在我的个人资料做相关的细节公开我们正在使用最新，最优秀的.NET库，。
The other problem was that most of the OPs I tried just didn't return information when queried with AX - I might have been doing something wrong (happens quite frequently :) ), but I had made relevant details public on my profiles and we're using the latest, most excellent .NET library, DotNetOpenId.
我们一定会在这里重温AX堆栈溢出，当我们得到多一点的时间，作为一个无缝的用户体验对我们来说非常重要！
We'll definitely revisit AX here on Stack Overflow when we get a little more time, as a seamless user experience is very important to us!
这篇关于OpenID属性交换 - 我应该使用它？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！