The non-functional requirements for CAS 3.0 are (original list by Bill Thompson):
- easy to install and configure
- helpful error reporting
- fail-fast when error or mis configured
- secure out of the box
- continuous operation (no chronic memory leaks)
- throughput (known throughput per memory/cpu)
As Andrew and I both suggested we may want to modify "secure out of the box" to "secure out of the box but demo-able". I.e. everything is secure except we enable the TestAuthenticationHandler.
We've already taken some steps for this. The handler is enabled, but we have a warning on the default UI pages about it being a test handler. The handler itself also logs a WARN message about the fact that it should not be used in production.