RCDevs OpenID Provider is an OpenID 1.1 and 2.0 provider with simple registration and multiple OpenID URL formats. Compared to other OpenID provider implementations, RCDevs OpenID Provider is extremely easy to implement: provided that you have a working WebADM server, installation just consists of adding the OpenID WebApp in WebADM and adding a markup in the index page of your public Web site. The RCDevs OpenID Provider works with LDAP and OpenOTP authentication back-ends. With OpenOTP, your OpenID users can authenticate with any OpenOTP one-time password mechanism (Soft Tokens, SMSOTP, MailOTP, Yubikey, MobileOTP). RCDevs OpenID Provider supports both query-string-based OpenID URLs and hostname-based OpenID URLs. An example of the format using a query string is "http://rcdevs.com/?user=myuser&domain=mydomain" and an example of the format using a hostname is "http://myuser.mydomain.rcdevs.com/".
epers stands for "Erlang persistence". As the name suggests, it tries to make it easy to use databases in Erlang programs, to make the language a little more agile, and (humbly) offer a nice adapter for several databases, hiding their implementation details (and the API of the library/framework/driver used to communicate with them). To achieve this, it aims to offer a somewhat consistent API to define and work with your model, while at the same not coupling your code too tightly to it.
GA4PHP is a class for PHP that allows a coder to provide a method for allowing two-factor authentication for users. Primarily focused on the Google authenticator for iOS, Blackberry, and Android, the system can also support hardware and software tokens based on the TOTP and HOTP standards. The system is designed such that a programmer would simply extend the PHP class to provide storage for the token data.