0a96753700978818eeaf3883a4e13423a32ce6b2
[java-idp.git] / src / conf / IQ-metadata.xml
1 <EntitiesDescriptor
2     xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
3     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
4     xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
5     xmlns:shibmeta="urn:mace:shibboleth:metadata:1.0"
6     xsi:schemaLocation="urn:oasis:names:tc:SAML:2.0:metadata ../schemas/saml-schema-metadata-2.0.xsd urn:mace:shibboleth:metadata:1.0 ../schemas/shibboleth-metadata-1.0.xsd http://www.w3.org/2000/09/xmldsig# ../schemas/xmldsig-core-schema.xsd"
7     Name="urn:mace:inqueue"
8     validUntil="2010-01-01T00:00:00Z">
9
10     <Extensions>
11                 <!-- This extension contains the list of CAs used by InQueue entities.  -->
12         <shibmeta:KeyAuthority VerifyDepth="1">
13                 <!-- Verisign -->
14             <ds:KeyInfo>
15                 <ds:X509Data>
16                     <ds:X509Certificate>
17 MIICNDCCAaECEAKtZn5ORf5eV288mBle3cAwDQYJKoZIhvcNAQECBQAwXzELMAkG
18 A1UEBhMCVVMxIDAeBgNVBAoTF1JTQSBEYXRhIFNlY3VyaXR5LCBJbmMuMS4wLAYD
19 VQQLEyVTZWN1cmUgU2VydmVyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk0
20 MTEwOTAwMDAwMFoXDTEwMDEwNzIzNTk1OVowXzELMAkGA1UEBhMCVVMxIDAeBgNV
21 BAoTF1JTQSBEYXRhIFNlY3VyaXR5LCBJbmMuMS4wLAYDVQQLEyVTZWN1cmUgU2Vy
22 dmVyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIGbMA0GCSqGSIb3DQEBAQUAA4GJ
23 ADCBhQJ+AJLOesGugz5aqomDV6wlAXYMra6OLDfO6zV4ZFQD5YRAUcm/jwjiioII
24 0haGN1XpsSECrXZogZoFokvJSyVmIlZsiAeP94FZbYQHZXATcXY+m3dM41CJVphI
25 uR2nKRoTLkoRWZweFdVJVCxzOmmCsZc5nG1wZ0jl3S3WyB57AgMBAAEwDQYJKoZI
26 hvcNAQECBQADfgBl3X7hsuyw4jrg7HFGmhkRuNPHoLQDQCYCPgmc4RKz0Vr2N6W3
27 YQO2WxZpO8ZECAyIUwxrl0nHPjXcbLm7qt9cuzovk2C2qUtN8iD3zV9/ZHuO3ABc
28 1/p3yjkWWW8O6tO1g39NTUJWdrTJXwT4OPjr0l91X817/OWOgHz8UA==
29                     </ds:X509Certificate>
30                  </ds:X509Data>
31             </ds:KeyInfo>
32             <!-- Bossie -->
33             <ds:KeyInfo>
34                 <ds:X509Data>
35                     <ds:X509Certificate>
36 MIIC6zCCAlSgAwIBAgICAlQwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVT
37 MRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoT
38 F1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJ
39 bmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBNYXN0ZXIgQ0Eg
40 LS0gMjAwMjA3MDFBMB4XDTAyMDYzMDIyMTYzOVoXDTI5MTExNjIyMTYzOVowgakx
41 CzAJBgNVBAYTAlVTMRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlz
42 b24xIDAeBgNVBAoTF1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJE
43 aXZpc2lvbiBvZiBJbmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBL
44 SSBNYXN0ZXIgQ0EgLS0gMjAwMjA3MDFBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB
45 iQKBgQDJ3FDZym9Ja94DP7TUZXf3Vu3CZwqZzYThgjUT2eBJBYVALISSJ+RjJ2j2
46 CYpq3wesSgWHqfrpPnTgTBvn5ZZF9diX6ipAmC0H75nySDY8B5AN1RbmPsAZ51F9
47 7Eo+6JZ59BFYgowGXyQpMfhBykBSySnvnOX5ygTCz20LwKkErQIDAQABoyAwHjAP
48 BgNVHRMBAf8EBTADAQH/MAsGA1UdDwQEAwIBpjANBgkqhkiG9w0BAQQFAAOBgQB1
49 8ZXB+KeXbDVkz+b2xVXYmJiWrp73IOvi3DuIuX1n88tbIH0ts7dJLEqr+c0owgtu
50 QBqLb9DfPG2GkJ1uOK75wPY6XWusCKDJKMVY/N4ec9ew55MnDlFFvl4C+LkiS2YS
51 Ysrh7fFJKKp7Pkc1fxsusK+MBXjVZtq0baXsU637qw==
52                     </ds:X509Certificate>
53                  </ds:X509Data>
54             </ds:KeyInfo>
55         </shibmeta:KeyAuthority>
56     </Extensions>
57
58         <!--
59         This is a starter set of metadata for the example system used within the
60         InQueue test federation. The InQueue deployment guide describes how to use
61         metadatatool or siterefresh to pick up the most current signed files.
62         Ordinarily a single EntityDescriptor would contain IdP/AA or SP information,
63         but not both. The sample site for InQueue just happens to contain both.
64         -->
65
66         <!-- Each IdP or SP is given an EntityDescriptor with its unique providerId/entityID. -->
67         <EntityDescriptor entityID="urn:mace:inqueue:example.edu">
68                 
69                 <!-- A Shib IdP contains this element with protocol support as shown. -->
70                 <IDPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:1.1:protocol urn:mace:shibboleth:1.0">
71                         <Extensions>
72                                 <!-- This is a Shibboleth extension to express attribute scope rules. -->
73                         <shib:Scope xmlns:shib="urn:mace:shibboleth:metadata:1.0">example.edu</shib:Scope>
74                         </Extensions>
75                         
76                         <!--
77                         One or more KeyDescriptors tell SPs how the IdP will authenticate itself. A single
78                         descriptor can be used for both signing and for server-TLS. You can place an
79                         X.509 certificate directly in this element for the simplest use cases. This
80                         example is more advanced, with the key/certificate identified by common name.
81                         The certificate is then validated using the KeyAuthority extension element up
82                         above.
83                         -->
84                         <KeyDescriptor use="signing">
85                             <ds:KeyInfo>
86                                 <ds:KeyName>wayf.internet2.edu</ds:KeyName>
87                             </ds:KeyInfo>
88                         </KeyDescriptor>
89                         
90                         <!-- This tells SPs that you support only the Shib handle format. -->
91                         <NameIDFormat>urn:mace:shibboleth:1.0:nameIdentifier</NameIDFormat>
92                         
93                         <!-- This tells SPs how and where to request authentication. -->
94                         <SingleSignOnService Binding="urn:mace:shibboleth:1.0:profiles:AuthnRequest"
95                             Location="https://wayf.internet2.edu/shibboleth-1.2/HS"/>
96                 </IDPSSODescriptor>
97                 
98                 <!-- Most Shib IdPs also support SAML attribute queries, so this role is also included. -->
99                 <AttributeAuthorityDescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:1.1:protocol">
100                         <Extensions>
101                                 <!-- This is a Shibboleth extension to express attribute scope rules. -->
102                         <shib:Scope xmlns:shib="urn:mace:shibboleth:metadata:1.0">example.edu</shib:Scope>
103                         </Extensions>
104                         
105                         <!--
106                         Note that because TLS with certificate validation is used, there is no KeyDescriptor
107                         needed. Since server TLS is used to authenticate the AA, its "key name" is implicit
108                         in the URL used to connect to it. If you were to place the certificate directly
109                         in the metadata in the role above, you'll also need a copy here.
110                         -->
111                         
112                         <!-- This tells SPs how and where to send queries. -->
113                         <AttributeService Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding"
114                             Location="https://wayf.internet2.edu/shibboleth-1.2/AA"/>
115                             
116                         <!-- This tells SPs that you support only the Shib handle format. -->
117                         <NameIDFormat>urn:mace:shibboleth:1.0:nameIdentifier</NameIDFormat>
118                 </AttributeAuthorityDescriptor>
119                 
120                 <!-- A Shib SP contains this element with protocol support as shown. -->
121                 <SPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:1.1:protocol">
122                 
123                         <!--
124                         One or more KeyDescriptors tell IdPs how the SP will authenticate itself. A single
125                         descriptor can be used for both signing and for client-TLS. You can place an
126                         X.509 certificate directly in this element for the simplest use cases. This
127                         example is more advanced, with the key/certificate identified by common name.
128                         The certificate is then validated using the KeyAuthority extension element up
129                         above.
130                         -->
131                         <KeyDescriptor>
132                             <ds:KeyInfo>
133                                 <ds:KeyName>wayf.internet2.edu</ds:KeyName>
134                             </ds:KeyInfo>
135                         </KeyDescriptor>
136                         
137                         <!-- This tells IdPs that you support only the Shib handle format. -->
138                         <NameIDFormat>urn:mace:shibboleth:1.0:nameIdentifier</NameIDFormat>
139                     
140                         <!--
141                         This tells IdPs where and how to send authentication assertions. Mostly
142                         the SP will tell the IdP what location to use in its request, but this
143                         is how the IdP validates the location and also figures out which
144                         SAML profile to use.
145                         -->
146                     <AssertionConsumerService index="0"
147                         Binding="urn:oasis:names:tc:SAML:1.0:profiles:browser-post"
148                         Location="https://wayf.internet2.edu/Shibboleth.shire"/>
149                 </SPSSODescriptor>
150                 
151                 <!-- This is just information about the entity in human terms. -->
152                 <Organization>
153                     <OrganizationName xml:lang="en">Example State University</OrganizationName>
154                     <OrganizationDisplayName xml:lang="en">Example State University</OrganizationDisplayName>
155                     <OrganizationURL xml:lang="en">http://shibboleth.internet2.edu/</OrganizationURL>
156                 </Organization>
157                 <ContactPerson contactType="technical">
158                     <SurName>InQueue Support</SurName>
159                     <EmailAddress>inqueue-support@internet2.edu</EmailAddress>
160                 </ContactPerson>
161                 
162         </EntityDescriptor>
163
164 </EntitiesDescriptor>