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:

http[s]://localhost/idp/profile/admin/mdquery?entityID=https%3A%2F%2Fsp.example.org%2Fsp

The same thing on the command line would be:

$ /opt/shibboleth-idp/bin/mdquery.sh -e https://sp.example.org/sp

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.

Browser not supported