Shibboleth Developers

["Scott Cantor" <>]

The java metadata plugin is checked in. It's missing a couple of bits we're
not using yet, mainly attribute push stuff, but all the current
functionality is there for the old Shib format and the new SAML profile. The
IdP changes are minimal at this point, but Walter can take a look.

Howard, I had to take more guesses about the SP, mainly because I was
ripping out the xmlbeans copies, and I didn't understand all the plugin
stuff. Java shouldn't need indirect reflection into the plugin layer like
C++ does, so I don't know what that's all for.

For now, I tried to wrap the new plugin inside of the serviceprovider
metadata plugin class and hope it will work for the time being, and you'll
have to review it.

One question that came up on the call about access to the keys, I think that
if we add Extension content to carry certificates, I'll just go ahead and
extend the metadata API with Shib-specific sub-interfaces that expose that
information. That's how I handled the Domain elements for the attribute
scoping anyway. It works pretty well.

The trust plugins shouldn't need to manage any of that data, or have access
to the XML data feed, they should be able to cast down and locate extended
material when they need it. That way there's only one copy of the metadata
pathname in the config file instead of duplicating it for each type of
plugin once there's only one file.

-- Scott