Managing Metadata using saml2meta
saml2meta is used to manage the SAML v2 metadata. The following table describes the saml2meta subcommands specific to metadata management.
Table 3–1 saml2meta Subcommands for Managing Metadata|
Subcommand |
Description |
|---|---|
|
import |
Loads standard and extended metadata in XML format into a local configuration data store. Note – Either -m or -x must be used. Both can also be used. |
|
export |
Exports standard and extended metadata in XML format from a local configuration data store. Note – Either -m or -x must be used. Both can also be used. |
|
template |
Generates a metadata configuration file for either type of hosted provider (service or identity) with defined values for default metadata properties. The generated file can be modified for use with import. |
|
delete |
Removes standard or extended metadata from a local configuration data store. |
|
list |
Generates a list of all the entity identifiers on the system. |
Following are some examples on how you might use saml2meta. See The saml2meta Command-line Reference for explanations of the options used.
-
The following command example will create both a standard and an extended metadata configuration file for service provider sp.sun.com:
# saml2meta template -u amadmin -w password -e sp.sun.com -s /sp -m spMeta.xml -x spExtended.xml
The standard metadata is defined in spMeta.xml and the extended metadata is defined in spExtended.xml.
-
This command example will import the created files into the local configuration data store:
# saml2meta import -u amadmin -w password -m spMetadata.xml -x spExtended.xml
Note –Remember to delete old metadata before you import modified files.
- © 2010, Oracle Corporation and/or its affiliates