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
This page has been created from a template that uses "zones." To proceed:
  1. Edit the page
  2. Replace sample content within each zone-data tag
  3. Remove this notice
  4. Save the page
  5. When you are ready for review, remove the Under Construction notice
Under Construction
This proposal is under construction and is not ready for review.

<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
Proposers Teemu Välimäki
Revision 1.0 - 3 March 2008: Initial (wiki revision: 3)

Table of Contents

1. Overview

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

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

Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.

  • Milestone 1: design notes will be published here
  • Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
  • Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
  • Milestone 4: Unit tests exist, work, and are checked into SVN.
  • Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

  • Milestone #: [DONE] Unit tests ...

7. Class Index

  • Zend_Auth_Adapter_Cas

8. Use Cases


9. Class Skeletons


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