I have a membership site using ASP.NET default membership setting. User accounts are free, with the option to pay for activation of other key parts of the site.
In keeping with the nature of the site, that is, built-in Google maps, street browsing, and using the Google CDN to host jQuery / jQueryUI for me ... it would be nice to offload authentication.
Also, it is in beta ... means that I can erase the slate if necessary. I have no payment clients yet. If I stick to what I have, it would be much harder to change later.
Here is one point that bothers me. While the main users are Americans (US service members), the main customer is Japanese. Will the OpenID implementation be problematic in this situation? Has anyone tried to use the authentication system only for OpenID on their membership site for Japanese users?
A few questions:
What happens when a visitor does not have OpenID-based login accounts?
Should I use a service like RPX or roll my own?
What are common errors when using the OpenID authorization system?
, OpenID , . X, Y1, Y2,..., Yn, , , X , Y .... .
, OpenID , . , , , OpenID, , OpenID .
, SO, , . , , , .
, , . .
: OpenID , SO. , , . -, SO , . Google, . , , , - . , , . , , , . , - . , Google. . , , SO, . , . , , , , , OpenID.
OpenID , . .
OpenID , . -, " Yahoo ID!". , , . OpenID. , , , .
OpenID. . RPX - , , . , ASP.NET, DotNetOpenAuth, RPX.