Comment out most of the examples. The example resolver and filter are now functional...
authorlajoie <lajoie@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Wed, 9 Jan 2008 13:43:42 +0000 (13:43 +0000)
committerlajoie <lajoie@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Wed, 9 Jan 2008 13:43:42 +0000 (13:43 +0000)
git-svn-id: https://subversion.switch.ch/svn/shibboleth/java-idp/trunk@2533 ab3bd59b-922f-494d-bb5f-6f0a3c29deca

resources/conf/attribute-filter.xml
resources/conf/attribute-resolver.xml

index 5372faf..724a579 100644 (file)
@@ -1,8 +1,8 @@
 <?xml version="1.0" encoding="UTF-8"?>
 
 <!-- 
-    This file is an EXAMPLE configuration file.  Deployers should NOT attempt to use this 
-    without modifying it for their environment.
+    This file is an EXAMPLE policy file.  While the policy presented in this 
+    example file is functional, it isn't very interesting.
     
     Deployers should refer to the Shibboleth 2 documentation for a complete list of components 
     and their options.
@@ -30,6 +30,7 @@
         Release eduPersonEntitlement and the permissible values of eduPersonAffiliation
         to any SP that is a member of InCommon, UK federation, or SWITCHaai
     -->
+    <!--
     <AttributeFilterPolicy>
         <PolicyRequirementRule xsi:type="basic:OR">
             <basic:Rule xsi:type="saml:AttributeRequesterInEntityGroup" groupID="urn:mace:incommon" />
         </AttributeRule>
 
     </AttributeFilterPolicy>
+    -->
 
     <!-- 
         Release the given name of the user to our portal service provider
     -->
+    <!--
     <AttributeFilterPolicy>
         <PolicyRequirementRule xsi:type="basic:AttributeRequesterString" value="urn:example.org:sp:myPortal" />
 
@@ -65,5 +68,6 @@
             <PermitValueRule xsi:type="basic:ANY" />
         </AttributeRule>
     </AttributeFilterPolicy>
+    -->
 
 </AttributeFilterPolicyGroup>
\ No newline at end of file
index f4843ee..9b32800 100644 (file)
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 
 <!-- 
-    This file is an EXAMPLE configuration file.  Deployers should NOT attempt to use this 
-    without modifying it for their environment.  In particular, deployers will need to edit 
-    data connector configurations.
+    This file is an EXAMPLE configuration file.  While the configuration presented in this 
+    example file is functional, it isn't very interesting.  However, there are lots of example
+    attributes, encoders, and a couple example data connectors.
     
     Not all attribute definitions, data connectors, or principal connectors are demonstrated.
     Deployers should refer to the Shibboleth 2 documentation for a complete list of components 
@@ -27,6 +27,7 @@
     <!-- ========================================== -->
 
     <!-- Schema: Core schema attributes-->
+    <!--
     <resolver:AttributeDefinition id="uid" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
         sourceAttributeID="uid">
         <resolver:Dependency ref="myLDAP" />
         <resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
             name="urn:oid:2.5.4.49" friendlyName="distinguishedName" />
     </resolver:AttributeDefinition>
+     -->
 
     <!-- Schema: inetOrgPerson attributes-->
+    <!--
     <resolver:AttributeDefinition id="departmentNumber" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
         sourceAttributeID="departmentNumber">
         <resolver:Dependency ref="myLDAP" />
         <resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
             name="urn:oid:2.16.840.1.113730.3.1.39" friendlyName="preferredLanguage" />
     </resolver:AttributeDefinition>
+    -->
 
-    <!-- Schema: eduPerson attributes-->
+    <!-- Schema: eduPerson attributes -->
+    <!--
     <resolver:AttributeDefinition id="affiliation" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
         sourceAttributeID="eduPersonAffiliation">
         <resolver:Dependency ref="staticAttributes" />
         <resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
             name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" friendlyName="eduPersonTargetedID" />
     </resolver:AttributeDefinition>
-
+    -->
 
     <!-- Name Identifier related attributes -->
     <resolver:AttributeDefinition id="transientId" xsi:type="TransientId" xmlns="urn:mace:shibboleth:2.0:resolver:ad">
     <!-- ========================================== -->
 
     <!-- Example Static Connector -->
+    <!--
     <resolver:DataConnector id="staticAttributes" xsi:type="Static" xmlns="urn:mace:shibboleth:2.0:resolver:dc">
         <Attribute id="eduPersonAffiliation">
             <Value>member</Value>
             <Value>urn:mace:dir:entitlement:common-lib-terms</Value>
         </Attribute>
     </resolver:DataConnector>
+    -->
 
     <!-- Example Relational Database Connector -->
+    <!--
     <resolver:DataConnector id="mySIS" xsi:type="RelationalDatabase" xmlns="urn:mace:shibboleth:2.0:resolver:dc">
         <ApplicationManagedConnection jdbcDriver="oracle.jdbc.driver.OracleDriver"
             jdbcURL="jdbc:oracle:thin:@db.example.org:1521:SomeDB" jdbcUserName="myid" jdbcPassword="mypassword" />
         <Column columnName="gzbtpid" attributeID="uid" />
         <Column columnName="fqlft" attributeID="gpa" type="Float" />
     </resolver:DataConnector>
+     -->
 
     <!-- Example LDAP Connector -->
+    <!--
     <resolver:DataConnector id="myLDAP" xsi:type="LDAPDirectory" xmlns="urn:mace:shibboleth:2.0:resolver:dc"
         ldapURL="ldap://ldap.example.org" baseDN="ou=people,dc=example,dc=org" principal="uid=myservice,ou=system"
         principalCredential="myServicePassword">
                 (uid=$requestContext.principalName)
             ]]>
         </FilterTemplate>
+     -->
 
     </resolver:DataConnector>