Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Auth_Adapter_Cas Component Proposal

Proposed Component Name Zend_Auth_Adapter_Cas
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Auth_Adapter_Cas
Proposers Teemu Välimäki
Revision 1.0 - 3 March 2008: Initial (wiki revision: 5)

Table of Contents

1. Overview

Zend_Auth_Adapter_Cas is authentication adapter for CAS (Central Authentication Service) single-sign on protocol.

"If the user ID and password are valid, CAS redirects the client to the application with a random number called a ticket. The application opens an HTTPS connection directly to CAS, and provides its own service identifier and the ticket. CAS then tells the application the user ID if the ticket is valid for that service identifier." tells Wikipedia.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will implement Zend_Auth_Adapter_Interface.
  • This component will authenticate CAS ticket against CAS server.
  • This component will return Zend_Auth_Result::SUCCESS when CAS ticket is valid.
  • This component will return Zend_Auth_Result::FAILURE when CAS ticket is invalid.
  • This component must support optional SSL / TLS encrypted transport.
  • This component will not handle user redirects.
  • This component will not try to read GET parameter for a CAS ticket, it must be supplied with the authentication().
  • This component will not save any data.

4. Dependencies on Other Framework Components

  • Zend_Http_Client

5. Theory of Operation

CAS authentication requires authenticator to actually go to the CAS sign-on page, so this must be done elsewhere by the developer. After successful authentication CAS server will redirect authenticator back to developer defined url. After this the developer must create code, that will pick CAS ticket and supply it to this Auth Adapter in its authenticate-method.

6. Milestones / Tasks

As CAS authentication process is simple it should not be a big task to make use of this component. This component might run into trouble with different versions of CAS.

  • Milestone 1: [DONE] Initial proposal published for review.
  • Milestone 2: Working prototype and some examples.
  • Milestone 3: Working prototype checked into the incubator supporting use cases.
  • Milestone 4: Unit tests exist, work, and are checked into SVN.
  • Milestone 5: Initial documentation exists.

7. Class Index

  • Zend_Auth_Adapter_Cas

8. Use Cases

UC-01 using CAS

9. Class Skeletons

]]></ac:plain-text-body></ac:macro>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.