[java-identity-provider] branch master updated: Remove links to the old wiki space.

[Scott Cantor]

This is an automated email from the git hooks/post-receive script.

scantor pushed a commit to branch master
in repository java-identity-provider.

View the commit online:
http://git.shibboleth.net/view/?p=java-identity-provider.git;a=commit;h=ba1625e427910f0fc17384533afe597f7f5b3c2c

The following commit(s) were added to refs/heads/master by this push:
       new  ba1625e   Remove links to the old wiki space.
ba1625e is described below

commit ba1625e427910f0fc17384533afe597f7f5b3c2c
Author: Scott Cantor <cantor.2 at osu.edu>
AuthorDate: Tue Mar 3 09:10:47 2020 -0500

    Remove links to the old wiki space.
---
 .../src/main/resources/conf/metadata-providers.xml | 36 +++++++++++-----------
 .../system/flows/saml/saml1/sso-abstract-flow.xml  |  2 --
 2 files changed, 18 insertions(+), 20 deletions(-)

diff --git a/idp-conf/src/main/resources/conf/metadata-providers.xml b/idp-conf/src/main/resources/conf/metadata-providers.xml
index 0667e71..fc81612 100644
--- a/idp-conf/src/main/resources/conf/metadata-providers.xml
+++ b/idp-conf/src/main/resources/conf/metadata-providers.xml
@@ -20,19 +20,19 @@
                         http://www.w3.org/2001/04/xmlenc# http://www.w3.org/TR/xmlenc-core/xenc-schema.xsd
                         http://www.w3.org/2009/xmlenc11# http://www.w3.org/TR/2013/REC-xmlenc-core1-20130411/xenc-schema-11.xsd">
 
-    <!-- ========================================================================================== -->
-    <!--                             Metadata Configuration                                         -->
-    <!--                                                                                            -->
-    <!--  Below you place the mechanisms which define how to load the metadata for SP(s) you will   -->
-    <!--  provide service to.                                                                       -->
-    <!--                                                                                            -->
-    <!--  Two examples are provided.  The Shibboleth Documentation at                               -->
-    <!--  https://wiki.shibboleth.net/confluence/display/IDP30/MetadataConfiguration                -->
-    <!--  provides more details.                                                                    --> 
-    <!--                                                                                            -->
-    <!--  NOTE.  This file SHOULD NOT contain the metadata for this IdP.                            -->
-    <!-- ========================================================================================== -->
-
+    <!--
+    Below you place the mechanisms which define how to load the metadata for SP(s) you will
+    provide service to.
+    
+    Some simple examples are provided. The documentation provides more details; in most cases,
+    the modern replacement for these older plugins are the "DynamicHTTPMetadataProvider" and
+    "LocalDynamic" variants, which provide dramatic memory savings and more reliable operation.
+     
+    NOTE: You do NOT need to load metadata for this IdP itself within this configuration.
+    -->
+    
+    
+    
     <!--
     Example HTTP metadata provider.  Use this if you want to download the metadata
     from a remote source.
@@ -42,7 +42,7 @@
     it with them via some out of band mechanism (e.g., a fingerprint on a secure page).
 
     The EntityRoleWhiteList saves memory by only loading metadata from SAML roles
-    that the IdP needs to interoperate with. 
+    that the IdP needs to interoperate with.
     -->
     
     <!--
@@ -61,8 +61,8 @@
 
     <!--
     Example file metadata provider.  Use this if you want to load metadata
-    from a local file.  You might use this if you have some local SPs
-    which are not "federated" but you wish to offer a service to.
+    from a local file. You use this if you have some local SPs which are not
+    "federated" but you wish to offer a service to.
     
     If you do not provide a SignatureValidation filter, then you have the
     responsibility to ensure that the contents on disk are trustworthy.
@@ -74,11 +74,11 @@
 
 
     <!--
-    Example CAS metadata source.
+    Example CAS metadata source for managing CAS services using SAML metadata.
     -->
 
     <!--
-    <MetadataProvider id="CasMetadata"
+    <MetadataProvider id="CASMetadata"
                       xsi:type="FilesystemMetadataProvider"
                       metadataFile="PATH_TO_YOUR_METADATA"
                       indexesRef="shibboleth.CASMetadataIndices" />
diff --git a/idp-conf/src/main/resources/system/flows/saml/saml1/sso-abstract-flow.xml b/idp-conf/src/main/resources/system/flows/saml/saml1/sso-abstract-flow.xml
index edc9096..7308b5c 100644
--- a/idp-conf/src/main/resources/system/flows/saml/saml1/sso-abstract-flow.xml
+++ b/idp-conf/src/main/resources/system/flows/saml/saml1/sso-abstract-flow.xml
@@ -3,8 +3,6 @@
     xsi:schemaLocation="http://www.springframework.org/schema/webflow http://www.springframework.org/schema/webflow/spring-webflow.xsd"
     abstract="true" parent="saml.abstract">
 
-    <!-- https://wiki.shibboleth.net/confluence/display/IDP30/SAML+1.1+Browser+SSO -->
-
     <!-- Bootstrap action has to be at the "top" of the flow after this flow prepends itself to parent. -->
     
     <action-state id="InitializeProfileRequestContext">

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.