...
For some helpful reference material on how native Spring syntax works, see:
- http://docs.spring.io/spring/docs/4.13.x/spring-framework-reference/html/beans.html
- http://docs.spring.io/spring/docs/4.13.x/spring-framework-reference/html/xsd-configconfiguration.html
Creating New Files
If you need to create your own Spring bean file to import or load into a service's resource set, the following template should be used. While usable to some degree in XML editors, the use of the "p" and "c" shorthand namespaces is not really schema-compatible and is designed for use inside Spring-aware tools such as the Eclipse STS plugin.
...
If you have a need to override or supplement existing flow mappings, you can supply two maps called shibboleth.FlowMap and shibboleth.FlowPatterns to replace, or more likely merge themselves with, the default beans mentioned above. The main use case for this would be to override the flow installed to one of the built-in locations or to register one of the built-in flows at an additional location. The practical reason you would do this would be to add additional endpoints for various services to fit some kind of unusual requirement.
Pre-Supplied Beans and useful classes
A standard IdP configuration provides you with many "named beans" which are there to simplify configuration. Examples include (but are not limited to) the many ActivationConditions which are available.
The PredefinedBeans topic details them all, as well as providing a list of other "useful class names".