www.flickr.com
tres frijoles' photos More of tres frijoles' photos
<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script -->
You are here: tearsoffire.org > Projects Web > SoftwareDevelopment > CrowdAuthenticationAuthorization r2 - 08 Apr 2009 - 18:22 - ChristopherPepe


Start of topic | Skip to actions

CrowdAuthenticationAuthorization

It is important to note that while Crowd handles authorization and authentication, the directories that are controlled by crowd and still also be used for authorization and authentication. Crowd offers some nice features such as single sign on and openID but that does not mean that applications can no longer directly connect to AD or OpenLDAP for these purposes as well.

A full list of supported applications and documentation is available here.

Apache

This works very much like the current Cosign solution. The apache configuration contains some information on how to talk to the Crowd server and the authentication and authorization is handled via an Apache Perl module. Any web application can now use crowd instead of Cosign including existing Turbogears applications (BENS), other protected sites (Netsys Wiki), or University single sign on solution.

Subversion

This builds off of the Apache module for subversion control.

Everything Else

Crowd has a SOAP API for connecting custom applications into Crowd.

-- ChristopherPepe - 25 Feb 2008

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding tearsoffire.org? Send feedback