内部注册，OpenID，Google Friend Connect，Facebook Connect和(等) [英] Inhouse registration vs. OpenID vs. Google Friend Connect vs. Facebook Connect vs. (etc)

问题描述

我正在尝试决定如何允许用户注册我的网站...有openID，clickpass，facebook连接，google朋友连接等，也可以是老式的内部输入用户名，电子邮件，密码等".

I'm trying to decide how to allow users to register for my website... there's openID, clickpass, facebook connect, google friend connect, etc, or the good old fashioned in-house "enter a username, email, password, etc."

简要查看如何设置OpenID 似乎需要做很多工作openID正常工作.

Looking briefly at How to set-up OpenID it seems like a lot of work to get openID working.

有人(或其他人)有为OpenID建立网站的经验吗?另外，有人知道这些方法的注册周转率是否比传统的内部"注册高?例如，如果您同时允许内部注册和openID，那么您有多少百分比的用户正在使用OpenID?

Does anyone have experience setting up a site for OpenID (or the others)? Also, does anyone know if these methods have a higher turnover rate of registration than the classic "inhouse" registration? For example.. if you allow both the in-house registration and openID, what percentage of your users are using OpenID?

一如既往，感谢您的输入.

As always, thanks for your input SO.

推荐答案

这实际上取决于网站的类型以及您的用户.

It really depends on the type of site and who your users are.

我们研究了在我们的电子商务商店(我们销售服装)中使用OpenID的可能性，并且得出的结论是，我们会竭尽全力来实施它.无论如何，我都不是世界上最聪明的软件开发人员，但是如果我勉强能全神贯注于此，只是为了获得StackOverflow的帐户(为什么我必须走到第三位)党的提供者?为什么要信任他们?如果我的帐户被盗，我的帐户会怎样?作为企业，如果客户要求我重设密码，我该怎么办?)，那么说我们的客户会不仅仅是轶事有问题.另外，对于任何电子商务企业，除非经过仔细考虑，否则通常不明智的做法是依赖第三方，尤其是对于登录等至关重要的事情.如果一个主要的OpenID提供程序崩溃，您将蒙受损失销售量.如果我们实现了OpenID，那么与本机登录机制相比，它肯定是另一种红发的子级子实现.

We looked at the possibility of using OpenID for our e-commerce store (we sell apparel), and the conclusion was that we would be flat out nuts to implement it. I'm not the smartest software developer in the world by any means, but if I could barely wrap my mind around it enough just to get an account for StackOverflow (Why do I have to go to some third party provider? Why should I trust them? What happens to my account if they go under? As a business, what do I do if a customer asks me to reset their password?), then it's not just anecdotal to say that our customers would have problems with it. In addition, for any e-commerce business, it's usually unwise to take on a third-party dependency unless carefully considered, and especially for something as critical as logging in. If a major OpenID provider were to go down, you'd be losing sales. If we implemented OpenID, it would definitely be an alternative, red-headed step child implementation when compared to the native sign in mechanism.

即使我们在内部注册了电子邮件地址和密码，我们也必须使用Amazon.com风格的登录表格，因为即使用户已经拥有帐户，用户仍会填写新客户"表格:

Even with our in-house registration of e-mail addresses and passwords, we had to use an Amazon.com style login form because users kept filling out the "new customer" form even when they already had an account:

登录屏幕.亚马逊的登录屏幕仍然是一个可以模拟的模型，从而最大程度地减少了新客户在未注册的情况下尝试登录的常见问题.亚马逊按线性顺序提出两个问题:(1)您的电子邮件地址是什么?" (2)您有Amazon.com密码吗?"对于第二个问题，用户可以选择两个单选按钮之一:否，我是新客户"或是，我有密码".许多其他站点并排显示新用户和已建立用户部分，从而通过输入字段的吸引将新用户转移到已建立用户部分. -Jakob Niesen， useit.com

当用户在导航两个字段和一个单选按钮时遇到麻烦时，您可以想象当使用多种身份验证机制呈现给他们时，会随之而来.

When users have trouble navigating two fields and a radio button, you can imagine the hilarity that ensues when they are presented with multiple authentication mechanisms.

如果您要实现一个旨在与Facebook或一些Web-2.0精明的消费者集成的面向社交的网站，则这些替代身份验证机制可能很有意义.不过，直到尘埃落定在OpenID上之前，我都不会将其添加到商业站点:没有人要求它.他们已经要求使用我们实现的PayPal和Google Checkout，但是那里只有很少的重叠.

If you're implementing a social-oriented Web site that is designed to integrate with Facebook or some of the Web-2.0-savvy consumers, then these alternative authentication mechanisms may make sense. Until the dust settles on OpenID, though, I wouldn't add it to a commercial site: nobody has asked for it. They have asked for PayPal and Google Checkout, which we implemented, but there's only a small amount of overlap there.

我的一般建议是拥有通常的内部用户名和密码机制，并可以通过这些替代的标识机制进行补充.但是要意识到，每种替代身份验证机制都存在客户混乱和增加客户支持的风险.

My general recommendation would be to have the usual in house username and password mechanism that can be supplemented by these alternative identification mechanisms. But realize that each alternative identification mechanism runs the risk of customer confusion and increased customer support.

我只有两美分；希望有帮助.

Just my two cents; hope that helps.

这篇关于内部注册，OpenID，Google Friend Connect，Facebook Connect和(等)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！