Resolution: Won't Fix
Affects Version/s: 2.4.0, 2.4.1, 2.4.x, 2.5.0, 2.5.2, 2.5.3, 2.5.4, 2.5.x, 2.6.x, 2.6.0
Fix Version/s: None
At present, CASifying Sakai requires a lot of manual fiddling around with various files. What I propose is to have the settings and dependencies added in by default so all one needs to do is to uncomment them, fill in the settings and they are done.
This also adds in the casclient.jar automatically so it doesnt need to be manually sourced.
This is a similar approach as to how the JLDAP provider works, the settings are in there already, they just need to be enabled.
The final part is in sakai.properties. A person setting up CAS needs to review the following sakai.properties
- Remove the username/password boxes at the top by setting this to false
top.login = false
- Let the container handle logins - ie to use single sign-on.
container.login = true
- Force logouts via CAS also
It would actually be great if a property in sakai.properties could turn on the settings in the webapp.