The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.
MetadataQuery
V3.4 adds an official mechanism for querying the IdP's Metadata resolver. This can be used as a debugging aid ("Is the IdP really seeing the metadata I think it is?") and also as a way of forcing specific entities into cache (which might be relevant for entities loaded via DynamicHTTPMetadataProvider or LocalDynamicMetadataProvider).
The underlying web interface, which is managed as an AdministrativeConfiguration, looks like this:
|
The same thing on the command line would be:
|
The parameters supported and their corresponding command line options are:
Query String | Command Line | Cardinality | Description |
|---|---|---|---|
entityID | --entityID, -e | Required | EntityID to find metadata for |
protocol | --protocol | Only 1 may be present | Protocol to find metadata role for |
saml1 | --saml1 | Queries for SAML 1.1 role | |
saml2 | --saml2 | Queries for SAML 2.0 role |
The tool essentially reproduces the results that would ordinarily be produced during relying party lookup in any of the "protocol" flows.