At Università di Parma, we deployed CAS 2 and uPortal 2.1.5 in late 2003, early 2004. We recently bought a couple of 64-bit machines to virtualize our servers; we'd like to start from webservers. Also we'd like to take this chance to upgrade CAS and uPortal to the lastest version.
I tried to install CAS 2.0.12 but we received an error while deploying a LDAP authenticating version: initializing CAS GenericHandler Logger... configuration file LoggerConf.xml is missing! CAS GenericHandler Logger configuration file is missing, setting default configuration... done. 0 [http-8080-Processor25] WARN CASGH - Configuration file genericHandler.xml is missing! The same error another person reported in this list in Apr, 2006. What is going wrong? When we tried CAS 3.0.6, the installation went well; also with LDAP authentication. Now we've got a problem in managing error messages; in particular login error messages. With version 2.x (now in production), I was able to modify login.jsp to behave differently (when the user put wrong credentials in the form) when specific parameters are passed to the page through a get operation: https://cas.unipr.it/login.jsp https://cas.unipr.it/login.jsp?service=http://... https://cas.unipr.it/login.jsp?adsu=1&service=http://... looks different after a wrong login. Is there a way to replicate the same behaviour in CAS 3.0.6, as simply as in CAS 2.x? best regards Marco Panella -- Ing. Marco Panella - tecnico di elaborazione dati Settore Innovazione Tecnologie Informatiche, Universita' di Parma Via G.P. Usberti, 17/A, I-43100, Parma, Italy Phone:+39 - 0521 - 90 - 5470 Fax: +39 - 0521 - 90 - 5469 _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
