Cookie based web authentication and single sign on system for largish intranets under a single domain where many, untrusted, people run their own web services. The server uses a private cookie scoped only for the client browser and the idcheck webserver which is always protected with SSL.
In addition to the common practise of using SSL for everything (which idcheck supports). The idcheck system can also be used to provide authentication to websites where you merely want to hide content from various people. For example, an intranet whose contents are available to thousands of people. This is, in fact, its main advantage and feature.
Please check the wiki pages for more info (link above).
Please submit patches or problems via the patches section (link above).
Please note that there are many idcheck RPMs on various web pages. Do not trust or use these versions. Always download them from sf!
Features
- Negotiates a single cookie with the https idcheck server that is not seen by other idchecked servers.
- Supports authentication to websites that dont really need https (e.g. large intranets)
- mod_idchecked webservers only see a cookie for them, which cannot be used against another mod_idchecked webserver.
- Requires an LDAP authentication server. e.g. OpenLDAP or AD.
- Can be integrated into Shibboleth to provide seemless web SS0.
- Normal apache configuration directives - nothing weird.
- IPv6 Experimental support.
- Uses mod_perl. Built with the apache portable runtime and libcurl. It should run on any system where these are suppported.
- So it can be integrated into web applications by simply looking at the REMOTE_USER variable that apache supplies. Anything that can be configured with HTTP Basic Authentication can be idchecked.
- Apache 2.0/2.2/2.4 supported.