...
2. Rebuild chef-tools module in Sakai (or full Sakai if you haven't made significant changes). Redeploy to Tomcat?just copying the WAR file doesn't seem to be enough. Verify that the source codes being changed are indeed modified at the Tomcat level. I have not found a maven goal that does this specifically..
3. Add top.login=false and container.auth=true to the sakai.properties file (this will turn off the password field on the login page)
4. Restart Tomcat: test that when you hit login (you shouldn't be localhost, use your IP so that the domain cookie is set correctly and can be seen), that the form that has the "DistAuth log in" button is there. When you click this button, you should be taken to DistAuth. Check error logs for the debugging code that I have in Cookies/Filters, etc.
...
1. Setup any Sakai usernames you would like to have login to the site.
(this step will be replaced by automated provisioning)
2. Login to Sakai as admin.
3. Click the Realms navigation link.
Click the /site/!admin realm.
Click the Grant Ability link.
Add any usernames in the provide ID box.
Save your changes to the Realm.
Click Done to commit your changes to the Sakai Realm.
4. Copy UCDDistAuthFilterAndWrapper.jar (attachment) into
Tomcat/common/lib to make it available to any web-app on
that instance of Tomcat.
(This contains the filter and request wrapper combined.)
5. Edit the sakai.properties file
(CATALINA_HOME/sakai/sakai.properties)
Turn on container.login in sakai.properties
If you do not have a line add
container.login = true
6.
Edit the web.xml file and set up servlet filter in
web.xml of $SAKAI_DEV\login\login\src\webapp\WEB-INF See the
example web.xml below. The order is important within the web.xml
...