...
There are significant differences in the OOB approach to configuration for new installs of V4.1 compared to V4.0 or upgraded systems. The tabs below (and elsewhere in the page) provide the relevant information for each version, and where applicable information on taking advantage of new approaches after upgrading.
Localtabgroupexpand | |||
---|---|---|---|
Localtab live |
| ||
The intercept/profile-intercept.xml file is where all supported interceptor flows are (usually minimally) described to the system. The file contains a Spring list bean named shibboleth.AvailableInterceptFlows. Descriptors are of a specific class, ProfileInterceptorFlowDescriptor, and generally the other options are handled with properties or with other XML configuration files. The Localtab live | | active | true
Expand | ||
---|---|---|
| ||
V4.1 introduces Modules, and most of the individual interceptor flows have been converted into modules that can be enabled and disabled. This approach is addressed within the pages that document all the flows. Every interceptor flow known to the system auto-registers itself and generally any other settings are documented on those individual pages.
Upgrading from V4.0 and EarlierThe information above focuses on the "as-delivered" V4.1 defaults, which are changed from earlier versions, and apply out of the box only to new installs. Upgraded systems, while they may contain combinations of old and new files, by design function the same as they used to for compatibility, and the new bits are generally ignored/overridden by the older settings. With V4.1, the use of XML to configure many basic features has been minimized and the original intercept/profile-intercept.xml file has been removed from new installations (but is still processed when present). With this release, all beans of type ProfileInterceptorFlowDescriptor are automatically recognized, obviating the need to define them by hand, which was the main purpose of the XML file. Instead, all of the built-in interceptor flows are wired up internally, and any settings required are (and, for the most part already were) handled with properties in the conf/idp.properties file. Any flow descriptor bean inside a list named shibboleth.AvailableInterceptFlows with a particular p For those wishing to migrate from the older approach to the newer approach (this is not required), removing intercept/profile-intercept.xml and setting any properties corresponding to non-default settings applied in the XML will provide equivalent behavior. |
...
Refer to the ProfileHandling developer material for more technical details on developing interceptor flows.
Reference
...
Beans
Bean ID | Type | Function |
---|---|---|
shibboleth.AvailableInterceptFlows | List of flow descriptors enumerating the interceptor flows available to the system (supplanted in V4.1 by autowiring of ProfileInterceptorFlowDescriptor beans, but you may need to create this bean if you wish to extend/alter the system-defined beans) | |
shibboleth.InterceptFlow | Abstract parent bean for defining new flow descriptor beans |