This email contained a disallowed file attachment. Raytheon does not allow email attachments that are considered likely to contain malicious code. For your protection this attachment has been removed.
If this email is from an unknown source, please simply delete this email. If this email was expected, and it is from a known sender, you may follow the below suggested instructions to obtain these types of attachments. Instruct the sender to enclose the file(s) in a ".zip" compressed file, and rename the ".zip" compressed file with a different extension, such as, ".rtnzip". Password protecting the renamed ".zip" compressed file adds an additional layer of protection. When you receive the file, please rename it with the extension ".zip". Additional instructions and options on how to receive these attachments can be found at:. http://security.it.ray.com/antivirus/extensions.html http://security.it.ray.com/news/2007/zipfiles.html Should you have any questions or difficulty with these instructions, please contact the Help Desk at 877.844.4712 Hi Kim, thanks for volunteering to help. I have a appended a small testing projekt that i have created for my personal testing. It requires that you have phpCAS in your PATH and only requires one central configuration for all testcases. It's basically most of the examples plus one interesting french ajax example that was posted a while back on the mailing list. My testing process is pretty much clicking through all examples and then throw it out into some small deployments i have. It would be very nice if you could do the same thing for release candidates and the final releases. A bit more audience with solid feedback during development would be a great help. Another problem for me is that i can only test very few real life applications and only against our own CAS servers that are version 3.3.5 and a bit custom with optional x509 support. I don't really have many proxy applications, no casified IMAP (yet), no real casified webservices, no Rubycas, no casified Moodle/Drupal/... and no IIS webservers etc. This could be an advanced testing task for you if you mainain any of those "stange" things and have the time to test them from time to time. There are so many possibilities that right now the my idea is to create some automated testing framework that requires little configuration and can be run automatically by developers during development and other willing testers before releases. I have created a JIRA issue to gather ideas for this future testing framework and how it should integrate into phpCAS. https://issues.jasig.org/browse/PHPCAS-66 Thanks, Joachim Am 09.06.2010 18:46, schrieb Cary, Kim: > Joachim, > > Thanks for your development work on phpcas! I would like to help you test new > releases of phpcas. Could you outline for me a test plan? For example, should > I just have a setup with all the phpcas examples working, debug on, and just > run through each of them for each release? Or, is there something more that's > needed? > > Kim -- Joachim Fritschi Hochschulrechenzentrum (HRZ) L1|01 Raum 248 Petersenstr. 30 64287 Darmstadt Tel. +49 6151 16-5638 Fax. +49 6151 16-3050 E-Mail: [email protected] -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
