I have more than one OpenID as I have tried out numerous. As people take up OpenID different suppliers are going to emerge I may want to switch provinders. As all IDs are me, and all are authenticated against the same email address, shouldn't I be able to log into stack overflow with any of them and be able to hit the same account?
我有多个OpenID,因为我尝试了很多。随着人们采用OpenID,不同的供应商将会出现,我可能想要转换启动器。由于所有ID都是我,并且所有ID都是针对同一个电子邮件地址进行身份验证的,因此我不应该使用其中任何一个登录到堆栈溢出并且能够访问同一个帐户吗?
6 个解决方案
#1
23
I think each site that implements OpenID would have to build their software to allow multiple entries for your OpenID credentials. However, just because a site doesn't allow you to create multiple entries doesn't mean you can't swap out OpenID suppliers.
我认为实现OpenID的每个站点都必须构建他们的软件,以允许您的OpenID凭据有多个条目。但是,仅仅因为某个站点不允许您创建多个条目并不意味着您无法更换OpenID供应商。
How to turn your blog into an OpenID
STEP 1: Get an OpenID. There a lots of servers and services out there you can use. I use http://www.myopenid.com
第1步:获取OpenID。你可以使用很多服务器和服务。我用http://www.myopenid.com
STEP 2: Add these two lines to your blog's main template in-between the <HEAD></HEAD> tags at the top of your template. Most all blog engines support editing your template so this should be an easy and very possible thing to do.
第2步:将这两行添加到博客主模板中,位于模板顶部的 标记之间。大多数博客引擎都支持编辑模板,因此这应该是一件容易且非常可能的事情。
Example:
<link rel="openid.server" href="http://www.myopenid.com/server" /> <link rel="openid.delegate" href=http://YOURUSERNAME.myopenid.com/ />
This will let you use your domain/blog as your OpenID.
这将允许您使用您的域/博客作为您的OpenID。
Credits to Scott Hanselman and Simon Willison for these simple instructions.
Scott Hanselman和Simon Willison对这些简单说明的信用。
Switch Your Supplier
Now that your OpenID points to your blog, you can update your link rel href's to point to a new supplier and all the places that you've tied your blog's OpenID will use the new supplier.
现在您的OpenID指向您的博客,您可以更新链接rel href以指向新供应商,并且您绑定博客的OpenID的所有地方都将使用新供应商。
#2
5
In addition to the meta tag sample by Otto, you should be aware whether your provider supports OpenID 2.0 (there are numerous improvements). If it does use meta tags as the following:
除了Otto的元标记示例之外,您应该知道您的提供程序是否支持OpenID 2.0(有许多改进)。如果它确实使用元标记如下:
<link rel="openid2.provider" href="http://www.loginbuzz.com/provider.axd" />
<link rel="openid2.local_id" href="http://example.loginbuzz.com/" />
<link rel="openid.server" href="http://www.loginbuzz.com/provider.axd" />
<link rel="openid.delegate" href="http://example.loginbuzz.com/" />
A good idea would also be to use secure links, but this could limit some relying parties from signing in. This could however be solved by providing a XRDS document.
一个好主意也是使用安全链接,但这可能会限制某些依赖方登录。但是,这可以通过提供XRDS文档来解决。
The really neat thing about XRDS is that you are able to specify multiple providers in this document. Say you have a bunch of different accounts all with different providers supporting different extensions. The relying party are then able to select the best match by itself. In the XRDS document you could also specify multiple URLs for each service, so that https is used when appropriate.
关于XRDS的真正优点是您可以在本文档中指定多个提供程序。假设您有许多不同的帐户,所有帐户都支持不同的扩展程序。然后依赖方能够自己选择最佳匹配。在XRDS文档中,您还可以为每个服务指定多个URL,以便在适当时使用https。
I would also recommend buying an i-name as it by design is more secure (the canonical ID - the i-number - associated with an i-name belongs to you even if the i-name expires).
我还建议购买一个i-name,因为它设计更安全(规范ID - i-number - 与i-name相关,即使i-name到期也属于你)。
#3
3
@prakesh
As long as you associate all of them to the same email address, i would think it would lead you to same account.
只要您将所有这些关联到同一个电子邮件地址,我认为它会引导您进入同一个帐户。
But whats your experience?
但你的经历是什么?
When I tried it out I got a whole new account with 0 rep and no steenkin badges. So at the moment SO does not allow multiple OpenID's to be associated with the one account
当我试用它时,我得到了一个全新的帐户,0代表没有steenkin徽章。所以目前SO不允许多个OpenID与一个帐户相关联
#4
2
Doesn't using multiple open-id providers sort of undermine the point of open id?
不使用多个open-id提供程序会破坏open id的意义吗?
No. Say you are using a Yahoo OpenID, but you decide to move to Google instead. Multiple OpenIDs per account allows you to associate your account with the Google OpenID, then deauthorize the Yahoo OpenID.
不。假设您使用的是Yahoo OpenID,但您决定转而使用Google。每个帐户有多个OpenID,您可以将自己的帐户与Google OpenID相关联,然后取消对Yahoo OpenID的授权。
#5
0
Doesn't using multiple open-id providers sort of undermine the point of open id?
不使用多个open-id提供程序会破坏open id的意义吗?
#6
0
The key here is to not change identities, ever. Change providers, but not identities. (this is like real life)
这里的关键是永远不要改变身份。改变提供者,但不改变身份。 (这就像现实生活)
So new users to OpenID should first consider what their identity could be.
因此,OpenID的新用户应首先考虑他们的身份。
Users that already have some kind of website they own should choose this URL and users without a website have these options:
已经拥有某种网站的用户应选择此网址,没有网站的用户可以选择以下网址:
- Get something like a blog to get a URL
- Buy an i-name (or a domain name)
- or use an identity provider supplied URL
获取类似博客的内容以获取网址
购买i-name(或域名)
或使用身份提供商提供的URL
In the case of the identity provider supplied URL, users need to be aware that if in the future they choose to delegate or change identities in some way that its essentially a new identity and that multiple identity support with RPs (and OPs) is limited (required usually to re-associate a local account on an RP site to a different OpenID identity).
在身份提供者提供的URL的情况下,用户需要知道,如果将来他们选择以某种方式委派或更改身份,其本质上是新身份以及RP(和OP)的多重身份支持是有限的(通常需要将RP站点上的本地帐户重新关联到不同的OpenID标识)。
#1
23
I think each site that implements OpenID would have to build their software to allow multiple entries for your OpenID credentials. However, just because a site doesn't allow you to create multiple entries doesn't mean you can't swap out OpenID suppliers.
我认为实现OpenID的每个站点都必须构建他们的软件,以允许您的OpenID凭据有多个条目。但是,仅仅因为某个站点不允许您创建多个条目并不意味着您无法更换OpenID供应商。
How to turn your blog into an OpenID
STEP 1: Get an OpenID. There a lots of servers and services out there you can use. I use http://www.myopenid.com
第1步:获取OpenID。你可以使用很多服务器和服务。我用http://www.myopenid.com
STEP 2: Add these two lines to your blog's main template in-between the <HEAD></HEAD> tags at the top of your template. Most all blog engines support editing your template so this should be an easy and very possible thing to do.
第2步:将这两行添加到博客主模板中,位于模板顶部的 标记之间。大多数博客引擎都支持编辑模板,因此这应该是一件容易且非常可能的事情。
Example:
<link rel="openid.server" href="http://www.myopenid.com/server" /> <link rel="openid.delegate" href=http://YOURUSERNAME.myopenid.com/ />
This will let you use your domain/blog as your OpenID.
这将允许您使用您的域/博客作为您的OpenID。
Credits to Scott Hanselman and Simon Willison for these simple instructions.
Scott Hanselman和Simon Willison对这些简单说明的信用。
Switch Your Supplier
Now that your OpenID points to your blog, you can update your link rel href's to point to a new supplier and all the places that you've tied your blog's OpenID will use the new supplier.
现在您的OpenID指向您的博客,您可以更新链接rel href以指向新供应商,并且您绑定博客的OpenID的所有地方都将使用新供应商。
#2
5
In addition to the meta tag sample by Otto, you should be aware whether your provider supports OpenID 2.0 (there are numerous improvements). If it does use meta tags as the following:
除了Otto的元标记示例之外,您应该知道您的提供程序是否支持OpenID 2.0(有许多改进)。如果它确实使用元标记如下:
<link rel="openid2.provider" href="http://www.loginbuzz.com/provider.axd" />
<link rel="openid2.local_id" href="http://example.loginbuzz.com/" />
<link rel="openid.server" href="http://www.loginbuzz.com/provider.axd" />
<link rel="openid.delegate" href="http://example.loginbuzz.com/" />
A good idea would also be to use secure links, but this could limit some relying parties from signing in. This could however be solved by providing a XRDS document.
一个好主意也是使用安全链接,但这可能会限制某些依赖方登录。但是,这可以通过提供XRDS文档来解决。
The really neat thing about XRDS is that you are able to specify multiple providers in this document. Say you have a bunch of different accounts all with different providers supporting different extensions. The relying party are then able to select the best match by itself. In the XRDS document you could also specify multiple URLs for each service, so that https is used when appropriate.
关于XRDS的真正优点是您可以在本文档中指定多个提供程序。假设您有许多不同的帐户,所有帐户都支持不同的扩展程序。然后依赖方能够自己选择最佳匹配。在XRDS文档中,您还可以为每个服务指定多个URL,以便在适当时使用https。
I would also recommend buying an i-name as it by design is more secure (the canonical ID - the i-number - associated with an i-name belongs to you even if the i-name expires).
我还建议购买一个i-name,因为它设计更安全(规范ID - i-number - 与i-name相关,即使i-name到期也属于你)。
#3
3
@prakesh
As long as you associate all of them to the same email address, i would think it would lead you to same account.
只要您将所有这些关联到同一个电子邮件地址,我认为它会引导您进入同一个帐户。
But whats your experience?
但你的经历是什么?
When I tried it out I got a whole new account with 0 rep and no steenkin badges. So at the moment SO does not allow multiple OpenID's to be associated with the one account
当我试用它时,我得到了一个全新的帐户,0代表没有steenkin徽章。所以目前SO不允许多个OpenID与一个帐户相关联
#4
2
Doesn't using multiple open-id providers sort of undermine the point of open id?
不使用多个open-id提供程序会破坏open id的意义吗?
No. Say you are using a Yahoo OpenID, but you decide to move to Google instead. Multiple OpenIDs per account allows you to associate your account with the Google OpenID, then deauthorize the Yahoo OpenID.
不。假设您使用的是Yahoo OpenID,但您决定转而使用Google。每个帐户有多个OpenID,您可以将自己的帐户与Google OpenID相关联,然后取消对Yahoo OpenID的授权。
#5
0
Doesn't using multiple open-id providers sort of undermine the point of open id?
不使用多个open-id提供程序会破坏open id的意义吗?
#6
0
The key here is to not change identities, ever. Change providers, but not identities. (this is like real life)
这里的关键是永远不要改变身份。改变提供者,但不改变身份。 (这就像现实生活)
So new users to OpenID should first consider what their identity could be.
因此,OpenID的新用户应首先考虑他们的身份。
Users that already have some kind of website they own should choose this URL and users without a website have these options:
已经拥有某种网站的用户应选择此网址,没有网站的用户可以选择以下网址:
- Get something like a blog to get a URL
- Buy an i-name (or a domain name)
- or use an identity provider supplied URL
获取类似博客的内容以获取网址
购买i-name(或域名)
或使用身份提供商提供的URL
In the case of the identity provider supplied URL, users need to be aware that if in the future they choose to delegate or change identities in some way that its essentially a new identity and that multiple identity support with RPs (and OPs) is limited (required usually to re-associate a local account on an RP site to a different OpenID identity).
在身份提供者提供的URL的情况下,用户需要知道,如果将来他们选择以某种方式委派或更改身份,其本质上是新身份以及RP(和OP)的多重身份支持是有限的(通常需要将RP站点上的本地帐户重新关联到不同的OpenID标识)。