Java LDAP SSL error 49, after some extensive googling, appears a bind credential failure. It appears that CAS does not intercept this exception for the case where the deployer has goofed the dn for the ldap bind account (in bind-search-bind mode). It just passes the error up to tomcat, which displays it to the browser.
In this case I had an extra cn= where I should have had an ou= Sigh! Thanks especially to Scott, and all the folks on the list who replied. Now to see if today's Apple java patch breaks what I've done so far! _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
