Configuration of IdP with Delegation extension

[Karla Borecky]

Hello all,

I'm wondering if anyone can help me with a few questions regarding
configuration of the IdP to use the delegation extension
(http://svn.shibboleth.net/view/extensions/java-idp-delegation/?sortdir=down)
.  I'm looking at the various instructions, old and new, for
configuring the IdP for delegation, and I ran across this in the
README file - from
http://svn.shibboleth.net/view/extensions/java-idp-delegation/trunk/doc/INSTALL.txt?revision=301&view=markup.
>From the instructions on editing the handler.xml file:

31	    c) Change all instances of the SAML 2 SSO profile handler to
the delegation-aware version by adding the namespace prefix from a),
e.g.:
32	
33	            <ProfileHandler xsi:type="SAML2SSO" ... />
34	
35	        becomes:
36	
37	            <ProfileHandler xsi:type="del:SAML2SSO" ... />
38	
39	        Note: it is also possible to support both delegation-aware
and non-delegation-aware endpoints simultaneously,
40	        but care must be taken in providing the correct metadata to
SP relying parties, consistent with the IdP's
41	        relying party configuration.

This concerned me. How does this affect all of the SPs I am talking to
now that *aren't* delegation-aware? However, in the version comments
for the extension, I see this:

   Delegation-aware SAML 2 SSO should have own communication profile ID,
   allows to co-exist without conflict with non-delegation aware SSO

This implies that delegation might now has its own profile - yay - but
this change is not reflected in the README file on how to configure
the IdP. Has anyone who has worked with this know what the handler.xml
and internal.xml file should look like now? (If I am correct in
assuming that the delegation-aware SAML2SSO does indeed have its own
profile now.)

Thanks for any help,
Karla B

-- 
Karla Borecky
Systems Administrator
ITS
Smith College
Northampton, MA 01063