You can use metadata as a basis for creating remote entities and forming a partnership. Metadata makes partnership configuration more efficient because many aspects of an entity are already defined in the metadata file. The file can then be imported to create a new partnership or remote entity.
You do not have to complete a partnership before exporting it. You can configure a portion of the partnership and then export it.
In the Federation Manager UI, you can export metadata from an existing partnership entry.
Note: In the Federation Manager UI, you can export metadata from an existing local asserting or relying entity. Be aware that when you export SAML 1.1 data, the terms used in the resulting metadata file are SAML 2.0 terms. This convention is dictated by the SAML specification. When you import the SAML 1.1 data, the terms are imported correctly using SAML 1.1 terminology.
When exporting from the partnership, the selected partnership is used as the basis of the export and you are not allowed to define a new partnership namethe system uses the name from the selected partnership.
To export partnership metadata
The View Federation Partnerships dialog displays.
The Export Metadata dialog opens.
If you are exporting a partnership in ACTIVE status, most of the fields are read-only; only the Validity Duration field and the alias drop-down list are editable.
Note: You can click Help for a description of fields, controls, and their respective requirements.
The metadata is exported to the specified XML file.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |