- Earn a $50 Amazon gift card for testing a new product from the makers of PBworks. Click here to apply.
- If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.
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.
– Community-ID is an OpenID implementation in PHP which is OpenID 2.0
compliant. Community-ID is build to 100% on Open Source software and is
release under the BSD license. Users can keep track of their trusted
sites and manage them. For Community-ID administrators statistics are
available to track registration of new users, authorized users per day
or the number of trusted sites. Administrators can set the site in
maintenance mode or send emails to all registered users. For user data
and authentication, admin can choose the default db storage, or to
connect to an LDAP server
– a lightweight OpenID based Internet identity server which includes a
simple profile webpage (Internet identity), can be installed as a single
user or a service to host many separate users, contact form, DH-SHA1
& DH-SHA256 support, OpenID 1.1 & OpenID 2.0 compliant, themed
“skins” which can be easily downloaded and added & it’s
multi-lingual. Note that development has been reopened and that a new
version is available at github: prairie-openid2-server.
- phpMyID – a standalone, single user identity provider.
- PHP OpenID Server.
- Clamshell – standalone, multi-user OpenID server.
- NetMesh InfoGrid LID PHP – supports OpenID as well as the LID protocol suite.
- SimpleID – A standalone provider, supporting multiple identities. Active development (May 2008).
- Heraldry PIP – Ruby on Rails identity server incubating within the Apache Software Foundation – Project retired (2007-06-09).
- Masquerade – Ruby on Rails OpenID server released under the MIT-license
- local-openid – Single-User Ephemeral OpenID server implemented with Sinatra released under the AGPLv3
- Packetizer OpenID Server
is a complete OpenID Provider server that you can freely download and
install to operate your own identity provider. It is compliant with
OpenID 2.0 and written entirely in Perl. It uses MySQL to store user,
association, and signature information.
– 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.
- 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 LDAP (eg Active Directory, OpenLDAP, etc) and
integrates with non-OpenID enabled applications such as Apache,
Subversion, and Google Apps.
- WSO2 Identity Solution,
WSO2 Identity Solution is a set of Relying Party components and an
Identity Provider to enable CardSpace and OpenID authentication.
- JOS(Java OpenID Server), JOS(Java OpenID Server) is a multi-domain, multi-user OpenID Provider based on OpenID4Java, Spring Framework, Hibernate, Velocity.
- OpenASelect Server,
OpenASelect is a Java based IdP server that supports OpenID 2.0, SAML
2.0 and more (federated) authentication protocols for professional
deployments. OpenASelect is available under the terms of the GNU Affero
- 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