I found a major issue regarding using Janrain.OpenId library on godaddy server. That library needs a .NET Full Trust permission to execute but godaddy host (mostly all other shared hosting services) allowed Medium Trust level for security reasons. GoDaddy.com ASP.NET 2.0 shared hosting servers use the default Medium trust level (source: http://help.godaddy.com/article.php?arti... ). That will cause a problem because OpenID requires full trust (source: http://code.google.com/p/dotnetopenid/is... I searched the internet regarding the solutions and workarounds and tried it but it did not solve the problem. The first solution I applied is I edited the AssemblyInfo.cs of Janrain.OpenId source. I added [assembly: AllowPartiallyTrustedCallers()] to the assembly part and recompiled and uploaded it to godaddy but the error still exists. The second solution is to override the settings in web.config and added trust level to high.

"OpenID: Great idea, bewildering consumer experience" is a thorough document saying that OpenID ... might have some problems. Some of the issues are: the site for OpenID is geared to developers, not users; finding an OpenID provider is troublesome; users won't understand that an OpenID is a location, not an actual identification.

OpenID basically centralizes login processes by requiring that users provide a URL to a site that provides their identity. When the user needs to "log in" to a site that participates in OpenID, the site redirects to the URL the user provided, where the user logs in; the OpenID provider then redirects back to the original site, providing the user's identity.

The advantage here is that users can log in on one server - the OpenID provider - for all sites participating, instead of potentially having passwords for each site on which the user has a login ID.