Creating a Metadata File for Your SP
If you've gotten this far, you have probably already chosen an Entity ID. If you have not, please see the Choosing your Shibboleth Entity ID topic.
What you should have finished so far
Before you continue with this page, you should have your shibboleth2.xml file created and configured.
Downloading the Metadata template for your server
When creating your metadata file, it's best to start with the SP generated Metadata and then customize it with your settings. The SP auto-generated metadata file will not work as is. You must customize this.
To get a copy of the file, you can use wget, curl, or a browser. Be sure that you use the protocol (http or https) and server name that browsers will access. The Shibboleth SP uses these values when generating the endpoint URLs in the metadata.
Download the generated metadata from apache using wget
wget -O metadata.xml https://www.servername.umn.edu/Shibboleth.sso/Metadata
Download the generated metadata from apache using curl
curl https://www.servername.umn.edu/Shibboleth.sso/Metadata > metadata.xml
From Windows, you'll have to open a web browser, type in the URL in the location bar, and choose File -> Save as... to save the file.
If this step fails, your application server is not configured properly for shibboleth. Please go back over the installation guides.
Customizing the Metadata file By adding Contact Information
To customize the metadata XML file, add the following information after the <md:SPSSODescriptor> section. Usually this is right before the second to the last line.
NOTE: If your organization contains reserved XML characters such as ampersand (&), greater than (>), or less than (<), be sure to escape them (& > or < respectively).
<md:Organization> <md:OrganizationName xml:lang="en">University of Minnesota, Department of Long Nomenclature</md:OrganizationName> <md:OrganizationDisplayName xml:lang="en">Department of Long Nomenclature</md:OrganizationDisplayName> <md:OrganizationURL xml:lang="en">http://www.dept.umn.edu/</md:OrganizationURL> </md:Organization> <md:ContactPerson contactType="support"> <md:GivenName>Authentication Support</md:GivenName> <md:EmailAddress>firstname.lastname@example.org</md:EmailAddress> </md:ContactPerson> <md:ContactPerson contactType="administrative"> <md:GivenName>FirstName</md:GivenName> <md:SurName>LastName</md:SurName> <md:EmailAddress>Your_x500@umn.edu</md:EmailAddress> </md:ContactPerson>
If you want to enable the guest account link on the login page, see the UMN IdP documention for Guest Accounts.
Adding additional servers
If you have more than one virtual (or physical) host sharing this entityID, you'll need to add endpoints for the other hostnames or you'll get the dreading Application Configuration Error from the IdP when you try to access them. See Add Additional Servers To Metadata for details.
Publishing your metadata
After you have your metadata file created, you may want to publish it to the Entity ID URL that you chose at the beginning of this process.
Testing Your Metadata
Move Your Metadata to Production
Example real live metadata file
You may browse these actual metadata files for reference. They are available here:
They contain examples of additional virtual hosts in a single entityID.