Disclaimer: The views and opinions expressed by bloggers (and those providing comments) are theirs alone and do not necessarily reflect the opinions of Unicon, Inc.
In which I summarize recent Unicon participation in and contributions to the Jasig CAS open source Java single sign-on product project, for a rather long meaning of “recent”.
So, attached is a quick dirty script I wrote to see if I can connect to an Apache Tomcat instance over HTTPS. This may be useful in the context of a CAS server deployment where ticket validation may fail as a result of an SSL certificate being absent or misconfigured in the keystore.
If you, like me, are going through a Shibboleth IdP install on a Windows 7 machine, after having configured all the necessary elements you may encounter an Apache Tomcat error that complains it can't bind on port 443.
To diagnose the problem, I ran:
netstat -o -n -a
Seeing extraneous Socket Timeout in your CAS log files? You may have overlooked the opportunity to turn off the single sign-out feature.
In which I discuss and provide screen shots related to an enhancement to CAS to automatically register the Services Management CAS web application.
Modern Jasig CAS server releases include a services management application for Web-based administration of the contents of the services registry. In some circumstances, you may want to disable its authentication and access control requirements. In this blog post I share how to do this.
Adam Franco has already concisely, cogently, helpfully, and momentum-building-ly posted to cas-user@ about phpCAS's migration to GitHub. My meta-comment? Truly excellent list post.