Combine credential blocks.
[java-idp.git] / src / conf / dist.idp.xml
1 <?xml version="1.0" encoding="UTF-8"?>
2
3 <!-- Shibboleth Identity Provider configuration -->
4
5         <IdPConfig 
6         xmlns="urn:mace:shibboleth:idp:config:1.0" 
7         xmlns:cred="urn:mace:shibboleth:credentials:1.0" 
8         xmlns:name="urn:mace:shibboleth:namemapper:1.0" 
9         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
10         xsi:schemaLocation="urn:mace:shibboleth:idp:config:1.0 shibboleth-idpconfig-1.0.xsd" 
11         AAUrl="https://idp.example.org:8443/shibboleth-idp/AA" 
12         resolverConfig="$SHIB_HOME$/etc/resolver.xml"
13         defaultRelyingParty="urn:mace:shibboleth:examples" 
14         providerId="https://idp.example.org/shibboleth">
15
16
17         <!-- This section contains configuration options that apply only to a site or group of sites
18                 This would normally be adjusted when a new federation or bilateral trust relationship is established -->
19         <RelyingParty name="urn:mace:shibboleth:examples" signingCredential="example_cred"> <!-- (signingCredential) must correspond to a <Credential/> element below -->
20                 <NameID nameMapping="shm"/> <!-- (nameMapping) must correspond to a <NameMapping/> element below -->
21         </RelyingParty>
22
23         <!-- InQueue example -->
24         <!--
25         <RelyingParty name="urn:mace:inqueue" signingCredential="inqueue_cred"> 
26                 <NameID nameMapping="shm"/>
27         </RelyingParty> -->
28         
29         
30         <!-- Configuration for the attribute release policy engine
31                 For most configurations this won't need adjustment -->
32         <ReleasePolicyEngine>
33                 <ArpRepository implementation="edu.internet2.middleware.shibboleth.aa.arp.provider.FileSystemArpRepository">
34                         <Path>$SHIB_HOME$/etc/arps/</Path>
35                 </ArpRepository>
36         </ReleasePolicyEngine>
37
38         
39     <!-- Logging Configuration
40                 The defaults work fine in this section, but it is sometimes helpful to use "DEBUG" as the level for 
41                 the <ErrorLog/> when trying to diagnose problems -->
42         <Logging>
43                 <ErrorLog level="WARN" location="$SHIB_HOME$/logs/shib-error.log" />
44                 <TransactionLog level="INFO" location="$SHIB_HOME$/logs/shib-access.log" />
45         </Logging>
46         <!-- Uncomment the configuration section below and comment out the one above if you would like to manually configure log4j -->
47     <!--
48         <Logging>
49                 <Log4JConfig location="file:///tmp/log4j.properties" />
50         </Logging> -->
51
52
53         <!-- This configuration section determines how Shibboleth maps between SAML Subjects and local principals.
54                 The default mapping uses shibboleth handles, but other formats can be added.
55                 The mappings listed here are only active when they are referenced within a <RelyingParty/> element above -->
56         <NameMapping 
57                 xmlns="urn:mace:shibboleth:namemapper:1.0" 
58                 id="shm" 
59                 format="urn:mace:shibboleth:1.0:nameIdentifier" 
60                 type="SharedMemoryShibHandle" 
61                 handleTTL="1800"/>
62
63
64         <!-- Determines how SAML artifacts are stored and retrieved
65                 The (sourceLocation) attribute must be specified when using type 2 artifacts -->
66         <ArtifactMapper implementation="edu.internet2.middleware.shibboleth.artifact.provider.MemoryArtifactMapper" />
67
68
69         <!-- This configuration section determines the keys/certs to be used when signing SAML assertions -->
70         <!-- The credentials listed here are used when referenced within <RelyingParty/> elements above -->
71         <Credentials xmlns="urn:mace:shibboleth:credentials:1.0">
72                 <FileResolver Id="example_cred">
73                         <Key>
74                                 <Path>$SHIB_HOME$/etc/idp-example.key</Path>
75                         </Key>
76                         <Certificate>
77                                 <Path>$SHIB_HOME$/etc/idp-example.crt</Path>
78                         </Certificate>
79                 </FileResolver>
80         
81                 <!-- InQueue example (Deployments would need to generate an InQueue-compatible certificate) -->
82                 <!--
83                 <FileResolver Id="inqueue_cred">
84                         <Key>
85                                 <Path>$SHIB_HOME$/etc/idp-inqueue.key</Path>
86                         </Key>
87                         <Certificate>
88                                 <Path>$SHIB_HOME$/etc/idp-inqueue.crt</Path>
89                         </Certificate>
90                 </FileResolver>
91                  -->
92         </Credentials>
93
94
95         <!-- Protocol handlers specify what type of requests the IdP can respond to.  The default set listed here should work 
96                 for most configurations.  Modifications to this section may require modifications to the deployment descriptor -->
97         <ProtocolHandler implementation="edu.internet2.middleware.shibboleth.idp.provider.ShibbolethV1SSOHandler">
98                 <Location>.+/shibboleth-idp/SSO</Location>
99         </ProtocolHandler>
100         <ProtocolHandler implementation="edu.internet2.middleware.shibboleth.idp.provider.SAMLv1_AttributeQueryHandler">
101                 <Location>.+:8443/shibboleth-idp/AA</Location>
102         </ProtocolHandler>
103         <ProtocolHandler implementation="edu.internet2.middleware.shibboleth.idp.provider.SAMLv1_1ArtifactQueryHandler">
104                 <Location>.+:8443/shibboleth-idp/Artifact</Location>
105         </ProtocolHandler>
106
107         
108         <!-- This section configures the loading of SAML2 metadata, which contains information about system entities and 
109                 how to authenticate them.  The metadatatool utility can be used to keep federation metadata files in synch.
110                 Metadata can also be placed directly within this these elements. -->
111         <MetadataProvider type="edu.internet2.middleware.shibboleth.metadata.provider.XMLMetadata"
112                 uri="$SHIB_HOME$/etc/example-metadata.xml"/>
113         
114         
115         <!-- InQueue example (Deployments would need to get updated InQueue metadata) -->
116         <!--
117         <MetadataProvider type="edu.internet2.middleware.shibboleth.metadata.provider.XMLMetadata"
118                 uri="$SHIB_HOME$/etc/IQ-metadata.xml"/> -->
119 </IdPConfig>
120