3.2 Testing

[Walter Forbes Hoehn (wassa)]

A few weeks back TomZ asked that I do some pre-release testing once things began to stabilize for 3.2.  Today I downloaded the most recent snapshot build and upgraded one of my local test servers from 3.1.1.  The upgrade went off without any real hitches.  The only thing that caused a momentary problem was that the semantics of the “-u” switch on reload-service.sh seem to have changed.  I had a number of local scripts that relied on this.  Easy enough to overcome.

Some things that I tested:

1. Upgraded 3.1.1 -> 3.2
2. Tried out a number of basic SAML2 SSO scenarios
3. Verified that my custom intercept flows continue to function appropriately
4. Tried out some basic CAS scenarios
5. Tested the following new features:  - IDP-678 (CAS Audit Logging) - IDP-615 (CAS Service Registry reload)  - IDP-742 (CAS Post Authentication Flows)
6. Ran some JMeter profile scripts - no issues encountered.  With 100 request threads, I was able to achieve 73.4 requests per second with a single node, which was actually slightly better than my previous results under 3.1.1.

-WFH