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.

...

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 now have to complete testing (legacy flows) and backfill on things I skipped (NameIdentifiers, StoredId) and other work which I shelved.

Scott 

Misc work:

• relax message types in actions/functions
• make lookup functions null and type-detecting where possible (return null instead of exception)

EndpointResolver completed, think we're about there re: binding config

Context population actions (oubound context, endpoint context)

RelyingParty design/usage -> starting to look at security contexts

Added message handler slots to ProfileConfig so we can interrupt current inbound chain to populate RP/Profile config and resolve the rest of the chain to run

Tom

• IDP-368 : setIdgetId() / getIdsetId() 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-334 'idp -t' ?
• JPAR-40 : Some artifacts still need to be uploaded to our third-party Nexus repo.
  • I have some dumb questions regarding "public key not found"
• JPAR-51 : Change Maven checksum policy from "warn" to "fail"
• JSPT-34 : Propose that Unicon host their own Jenkins for integration tests, start with the Tomcat 6.0.33+ trustManagerClassName + "trust all certs" trust manager
• Should message handlers be declared similar to actions rather than as a chain ?
  
  

...