Shibboleth Developer's Meeting, December 06, 2013

...

1. Resources
   1. No Shibboleth Resources used inside MDA or IDP now (just spring)
2. Services
   1. Currently under construction.
   2. SpringReloadableService is fully generic (and could load itself)
   3. Need to add failfast and reloadfrequency to idp.properties for AttributeResolver, AttributeFilter, Logback
   4. Need to move Mapper back into resolver (just as encoding is)
3. Spring integration
   1. Need to review context usage.
4. Also
   1. Generic Types
   2. Other cleanup
   3. Dependencies
   4. SPR-1112

Scott 

Uber-import into Nexus: think we should probably move the central-disabling stuff into the release profile

Should create some scripts to download artifacts from Central and then upload to Nexus. Maybe next round.

SP 2.5.3 release/advisory done. Some concerns about RHEL 6.5 with OpenSSL bump, but I probably overreacted and doubt this will be a problem.

This week:

• started reviewing RelyingParty skeleton code, interfaces back to OpenSAML for security config
• de-Springifying some foundational profile actions and moving a couple into OpenSAML
• some cleanup (renaming) on the AttributeEncoder layer
• looking at existing SAML profile code so we can start planning out that work

Would like to have a document akin to what I did for Authentication that lays out the messaging- and profile-related contexts (need help from Brent probably)

Do we have docs on Attribute-related contexts?

A question from Christoph: would getting some time from Halm help with consent layer?

Tom

Weeks in review :

• Branching from active flows http://shibboleth.net/pipermail/dev/2013-November/002946.html
• SP release
• ParserPool changes ?
• Dummy keys
• AttributeResolver being a Resolver
• Spring 4.0RC1
• Maven central
• Checkstyle plugin update
• Remove super() ?

...