Shibboleth Developer's Meeting, Feb 21, 2014
Attendees:
Call Administrivia
10:00 Central US / 11:00 Eastern US / 16:00 UK
Dial-in attendee identification.
Next week will be the last Friday of the month, so we would normally skip it. Any reason to meet ?
60 to 90 minute call window.
Brent
Daniel
Ian
We're now on Spring Framework 4 (4.0.2) and Spring Web Flow 2.3.3 (latest) and everything still works. Huzzah!
I have some dumb questions about logging, exclusions and Spring.
Rod
Finally managed to test a test webflow, and so now fitting in attribute resolver/C14N tests for the C14N stages implemented so far. Thus far most bug fixing has been to change NameDecoderException exceptions (which are fatal and stop the flow) to SubjectCanonicalizationException exceptions (which signal to try the next decoder). C14N cascading is working really well - the tests try as Transient, then CryptoTransient, then direct.
I now have to complete testing (legacy flows) and backfill on things I skipped (NameIdentifiers, StoredId) and other work which I shelved.
Scott
Tom
- IDP-368 : setId() / getId() either Identified/Identifiable or Named/Nameable or ?
- IDP-369 : custom prototype annotation or interface providing isPrototype() / getScope() ?
- IDP-375 : port audit and access logging, include error logging, any relevance to 'idp -t' ?
- Unicon : propose that they setup their own Jenkins for integration tests, start with the Tomcat 6.0.33+ trustManagerClassName + "trust all certs" trust manager
Other