Page Comparison

...

1. Edit the <MetadataProvider> tag, setting the legacyOrgNames attribute to true. (See NativeSPMetadataProvider for more information). We do this because at this time almost no federation metadata includes the discovery UI extensions. (See section 4. Metadata Considerations for more information).

   Code Block
   xml xml
   <MetadataProvider type="XML" uri="http://federation/metadata.xml" backingFilePath="federation.xml" legacyOrgNames="true" reloadInterval="7200"

    

   >

2. Edit the SSO tag (see NativeSPServiceSSO for details), removing the entityID attribute and adding a discoveryProtocol of "SAMLDS" and setting the discoveryURL attribute to the URL of the web page that will contain the EDS.

   Code Block
   xml xml
   <SSO discoveryProtocol="SAMLDS" discoveryURL="https://yoursp/path/to/EDS"> SAML2 SAML1 </SSO>

...

1. Edit the <MetadataProvider> tag, setting the legacyOrgNames attribute to true. (See NativeSPMetadataProvider for more information.) We do this because at this time almost no federation metadata includes the discovery UI extensions. (See section 4. Metadata Considerations for more information).

   Code Block
   xml xml
   <MetadataProvider type="XML" uri="http://federation/metadata.xml" backingFilePath="federation.xml" legacyOrgNames="true" reloadInterval="7200">

2. Edit the Sessions tag to add a discovery service feed.

   Code Block
   xml xml
   <Handler type="DiscoveryFeed" Location="/DiscoFeed"/>

    

3. Modify the <SessionInitiator> chain used by your deployment and make sure the last <SessionInitiator> element in the chain is of type="SAMLDS" and that it points to the web page containing the EDS. If an existing element of type="WAYF"is present you will need to remove it or comment it out.

   Code Block
   xml xml
   <!-- This is an example, it may not match yours exactly. --> <SessionInitiator type="Chaining" Location="/Login"> ... earlier elements ... <SessionInitiator type="SAMLDS" URL="https://yoursp/path/to/EDS"/> </SessionInitiator>

...