OpenID

Run your own identity server

Running your own identity server allows you to act as an OpenID Provider. You could run one just for yourself, for a community of users or, if you wish, for the general public. You do not need to register or obtain permission from anyone; you just need to run an OpenID identity server on your site. This requires the ability to install and run some software on your web server. Some existing OpenID identity server implementations are listed below.

  • PHP
  • Ruby
    • Heraldry PIP - Ruby on Rails identity server incubating within the Apache Software Foundation
    • Masquerade – Ruby on Rails OpenID server released under the MIT-license
  • Python
  • .NET
    • DotNetOpenId - library to add OpenId provider support to your web site or just give yourself an identity page on your web site that redirects to another provider. ASP.NET controls are also offered for ASP.NET web sites.
  • Java
    • NetMesh InfoGrid LID Java - supports OpenID as well as the LID protocol suite
    • Atlassian's Crowd, Java based identity management server that is free for open-source projects. Supports SREG, LDAP and integrates with non-OpenID enabled applications such as Apache and Subversion.
    • WSO2 Identity Solution, WSO2 Identity Solution is a set of Relying Party components and an Identity Provider to enable CardSpace and OpenID authentication.
  • Unknown / other
    • OpenLink Data Spaces (ODS) - a new generation Data Space platform for Semantic Web Presence that includes support for OpenID.
    • Gracie, a local-account provider that authenticates users against the local PAM system.
    • OpenLink Data Spaces, a platform for meshing Identity and Web Data such that all your data (Facebook, Del.cio.us, Flickr, RSS, Atom, OPML, and others data sources) is pegged to your OpenID via a Linked Data URI without any programming. In a nutshell you end up with an OpenID based Linked Data Space for all of you current and future Web protocols accessible data.