...

Note: the net.shibboleth.idp.profile.config.SecurityConfiguration currently uses the above interfaces directly, which may or may not be correct.  The current interfaces were intended to be more of the #1 effective runtime info components (despite the -Configuration naming convention).  At the very least we need to reconcile the "dynamic effective runtime" component notion with the "static configuration" component notion.

Also need to work out how much of this can and should be pushed down into OpenSAML, and what is really IdP-layer stuff.  In OpenSAML we at a minimum probably need basic impls of one form or another of all these interfaces.

Minor Work Items

...

Metadata Crypto Extension Support

We need to implement XMLObject providers for supporting the crypto selection extension(s) in SAML metadata.

XMLObject provider cleanup

• Unmarshalling
  
  • switch to QName-based handling for attribute names
• Namespace support:
  
  • implement deprecations, switch to NamespaceManager for everything

SOAP Client

We need one that works with the new message processing stuff, and that doesn't suck like the old one.

Artifact Resolution

Depends on SOAP client.  We never implemented in v2 message decoders that accepted and resolved inbound artifacts, b/c we needed a SOAP client that supported what we needed.