The Shibboleth V2 IdP and SP software have reached End of Life and are no longer supported. This documentation is available for historical purposes only. See the IDP v4 and SP v3 wiki spaces for current documentation on the supported versions.


This is a test program that can be used to exercise the attribute-processing subsystems and plugins in the SP to process a SAML assertion or a user's identifier.

Successful output consists of a textual summary of the resulting attribute information. Failure results in console-directed log messages and a negative return code.

To process a complete SAML assertion, it must be provided on the stdin stream. Otherwise, the following parameters must be used:


a SAML name identifier value


optional SAML name identifier format


entityID of an IdP


a protocolSupportEnumeration value to use in finding the IdP role in metadata


shortcut for "-p urn:oasis:names:tc:SAML:1.0:protocol"


shortcut for "-p urn:oasis:names:tc:SAML:1.1:protocol"


shortcut for "-p urn:oasis:names:tc:SAML:2.0:protocol"

In either mode:


optional applicationId to use in applying SP configuration, if other than "default"

An example of executing the resolvertest is given below:

./resolvertest -n _9f2d9fd62aa99cc43bf483045aeac123  -i -saml2 -f urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

The result of the processing will be to run the attribute extraction, filtering, and resolution subsystems against the input information. Support for queries comes from the use of the default resolution plugin. The output of the above command then could look like this:

./resolvertest -saml2 -f urn:oasis:names:tc:SAML:2.0:nameid-format:persistent \
-i -n FQdaogdLEj0iZZTIfdS3svc52WE= 
uid: haemmerle
affiliation: staff
surname: Hämmerle
givenName: Lukas
homeOrganizationType: others
gender: 1

In order to make attribute request to an Attribute Autority using a persistent Identifier, the Shibboleth Identity Provider needs to configure a PrincipalConnector for the persistent Name Identifier format in the attribute-resolver.xml configuration:

     <resolver:PrincipalConnector xsi:type="pc:StoredId" id="saml2Persistent"
        storedIdDataConnectorRef="myStoredId" />

Be sure to set the DataConnectorRef with the correct ID of a targetedID connector (e.g. "dc:ComputedId")