Page Comparison

...

Have a look at the Messages Translation page to find out how to download existing or create new translations of the IdPv3 messages.

Reference

Bean ID	Type	Default	Function
shibboleth.DefaultErrorView	String	%{idp.errors.defaultView:error}	Identifies the view name to use by default for Local events, generally left alone
shibboleth.EventViewMap	Map<String,String>	See errors.xml	Map that links event names to view names, generally used only for specialized flows that use a view to render their final output
shibboleth.LocalEventMap	Map<String,Boolean>	See errors.xml	Map that enumerates event names that should be classified as Local
shibboleth.SAML1StatusMappings	Map<String,List<QName>>	See errors.xml	Map of non-Local event names to SAML 1 StatusCode values (including substatus values)
shibboleth.SAML2StatusMappings	Map<String,List<String>>	See errors.xml	Map of non-Local event names to SAML 2 StatusCode values (including substatus values)
shibboleth.SOAPFaultCodeMappings	Map<String,QName>	See errors.xml	Map of non-Local event names to SOAP faultcode

Properties defined in idp.properties directly related to this configuration area follow:

Property	Type	Default	Function
idp.errors.detailed	Boolean	false	Whether to expose detailed error causes in status information provided to outside parties
idp.errors.signed	Boolean	true	Whether to digitally sign error responses in SAML or similar protocols, if signing is otherwise warranted (this can prevent a simple denial of service vector, since errors are simple to trigger)
idp.errors.

defaultView

defaultView	String	error	The default view name to render for exceptions and events
idp.errors.exceptionMappings ^3.2	Properties

		A property set mapping exception class names to error views. The matching by class name does not support wildcards, but does do substring matches (so it's not necessary to fully qualify the class).
idp.errors.excludedExceptions^3.2	Collection<Class>

Exception classes to ignore (causing them to bubble outward, so use with caution)

There is no direct compatibility with V2 error handling and the older interfaces to error information are not compatible.

...