Skip to end of metadata
Go to start of metadata

Proposed project:

CAS account management module

(CASAMM? Pronounced "chasm"?)

A sub/sister project for CAS 3.

Scope:

Extensions to the JA-SIG Central Authentication Service in support of integrated account management, including account creation, password creation, password reset, and administrative account blocking.
This project intends to provide extensions to the CAS server in a coding style and implementation stack similar or identical to core CAS server. This allows the core CAS server project to retain its focus on pure Authentication and being web SSO / Authentication service (helps stave off scope creep in the core project) while providing productized ready to rock and roll implementations of the next layer of commonly requested features. Providing these features makes CAS more marketable and viable as a WEB SSO solution (enhances the bullet list of features) while avoiding scope creep in the core project to go after that longer bullet list of features. Ideally, everybody wins: CAS can be marketed as even more of a one-stop-shop solution for your institution's SSO needs, while it remains the lean mean powerful SSO solution without creeping to do account management, authz, attributes, etc.

Resources:

In order for this project to succeed, we need interested parties willing to submit, validate, and own use cases, we need developers interested in developing, tracking, QAing, testing, etc., code, we need user experience designers interested in giving this a good feel out of the box demonstrating its potential and delivering real value to CAS deployers by providing something usable out of the box, and we need release engineers interested in weaving this together into a JA-SIG quality product.

Infrastructure:

As a JA-SIG project, CASAMM would take advantage of JA-SIG issue tracking (exist as a project in JA-SIG JIRA), JA-SIG wiki (a new Confluence space or pages within the CAS space?), potentially JA-SIG source control, though there are viable JA-SIG external alternatives (JavaForge example: http://www.javaforge.com/proj/summary.do?proj_id=625), SourceForge is successfully used by JA-SIG Hypercontent, Java .NET hosting, etc.)

Anticipated deliverables:

Sourcecode with additional Spring WebFlows actions, JSPs, documentation on how to make it go. A quickstart release of CAS 3 server with these extensions applied demonstrating the functionality. Enhancements to the JA-SIG-deployed CAS3 server to make use of these extensions.

Next steps

Gather requirements

Concretely, what account management functionality do you need from this module? Use cases. Requirements. Sketches of what this looks and feels like.

Gauge interest

Who's in? Who's interested in using this if it exists, and who's interested in doing work here? Do we have the interest to make this happen?

  • David Whitehurst - in(++(wink) if this is NOT an application (like service manager) that comes with CAS.
  • No labels