Get flash to fully experience Pearltrees
The Lightweight Directory Access Protocol ( LDAP ; pron.: / ˈ ɛ l d æ p / ) is an application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. [ 1 ] Directory services may provide any organized set of records, often with a hierarchical structure, such as a corporate email directory. Similarly, a telephone directory is a list of subscribers with an address and a phone number. LDAP is specified in a series of Internet Engineering Task Force (IETF) Standard Track Request for Comments (RFCs), using the description language ASN.1 .
Autentification, registration, identity
The CAS User Manual is the primary source of documentation for implementers of the Jasig CAS server component. For readers unfamiliar with CAS, the Overall Architecture section is a good starting point to learn what CAS is and how it works. Readers will learn that CAS is a multi-protocol SSO solution and they will want to review protocols to learn the use cases under which a particular protocol applies. Once review of background material is complete, readers should consider working through the CAS demonstration , which will provide a working product and an introduction to configuration. There are a few fundamental considerations to CAS configuration:
A manual walkthrough of CAS proxy tickets. This walkthrough was provided by David Spencer on the CAS Mailman list. When I was trying to understand the mechanisms involved in writing proxying applications using CAS, I found it very helpful to manually walkthrough the aquisition of a proxy ticket. The CAS server played itself in this exercise and I played all the other roles - user, proxying application and proxied application - simply by constructing URLs and feeding them into a web browser. The only part of the exercise that can't be done with just a web browser and careful URL construction is the part where CAS makes it's own callback to the proxying application.
The JA-SIG CAS Client for Java 3.1 is a reworking of the original Yale CAS Client and the newer JA-SIG CAS Client for Java 3.0. Both were excellent for different reasons: the Yale client had minimal dependencies and could get you up and running quickly while the JA-SIG client offered a more flexible configuration and conformed to more modern "best practices" but came with a large number of dependencies. The JA-SIG CAS Client for Java 3.1 looks to offer the best of both worlds. In its default configuration mode, it can be configured completely in the web.xml and has only one dependency, Commons Logging, which most applications use anyway. However, if you need the more advanced configuration you can easily configure the CAS client using Spring (and take its jars along with you Going forward, the JA-SIG CAS Client for Java 3.1 will be included in projects requiring a Java CAS Client, such as Spring Security .
Skip to end of metadata Go to start of metadata Shibboleth allows users to securely send trusted information about themselves to remote resources. This information may then be used for authentication, authorization, content personalization, and enabling single sign-on across a broad range of services from many different providers. The current stable release of the Identity Provider is V2.3.8 . There are no previous stable releases at this time. The current stable release of the Service Provider is V2.5.1 .
Author: Drew Mazurek Contributors: Version: 1.0 Release Date: May 4, 2005
Experiences CASifying applications Oracle applications ESUP-Portail distributions of CASified applications The ESUP-Portail download site offers links to a CASified Horde , a CASified phpBB , a CAS proxy for Sun One Calendar , and a CAS proxy for Apogee Web. Applications that come CASified