Shibboleth Developer's Meeting, April 04, 2014

...

Attendees: 

Call Administrivia

10:00 Central US / 11:00 Eastern US / 16:00 UK

Dial-in attendee identification.

...

• "Move the source attribute ID ..."  Can we postpone until I am present
• "Improve the relational database connector's connection pooling..." Do not feel I can make any input, but am interested in the result.  See also IDP-318
• "The ID attribute will be required for all policies".  I think we should drop this. It creates needless impedance for update. IDP-277 was the work item for this.  We do not require identification but if we do not have one we log (at warn) a generate identifier.  This is then used in all logging.  Reopen IDP-277 if we change our minds.
• "HTTP and File-backed HTTP provider will be merged into one implementation".  Interested in the outcome.
• "The signature validation filter will have options".  Can we postpone until I have looked at the code.  My instinct is that this should be done if easy.
• All other items I have no input to make but am interested in the outcome.

Scott

Tom

• OSJ-69 Change encoder even though it does not encode the same as the old encoder ?
• Properties :  Spring, Logback, and Jetty 9 support configuration via a properties file, but only Spring and Logback support nested properties. Spring and Logback do not use the same syntax for a default value. A workaround is to configure Jetty via Spring. The only property replacement supported for contextConfigLocation in web.xml seems to be system properties and environment variables.

...

• Very basic Selenium tests for IdP v2 and v3 in github.
• https://jira.spring.io/browse/SWF-1617  'Support relative flow locations for flow registry base paths prefixed with "file:"' Complete. 2.4.0.RC1

Other

IdP v3 functionality open issues and JIRA housekeeping (30m)

...