...
The id property of each descriptor is not arbitrary. It MUST be prefixed by "intercept/" and it corresponds to a web flow definition. The predefined beans correspond to built-in flows. Creating a new flow involves not only describing the flow in this list, but ensuring the id matches a flow definition created inside flows/intercept/. Specifically, creating the custom flow "intercept/foo" requires that the flow definition file be named flows/intercept/foo/foo-flow.xml.
There are three intercept flows The following interceptor flows are provided with the software:
...
Refer to the ProfileHandling developer material for more technical details on developing interceptor flows.
Reference
Beans
| Bean ID | Type | Function |
|---|---|---|
| shibboleth.AvailableInterceptFlows | List<ProfileInterceptorFlowDescriptor> | List of flow descriptors enumerating the interceptor flows available to the system |
| shibboleth.DefaultInterceptFlows | List<ProfileInterceptorFlowDescriptor> | List of built-in interceptor flows, into which user-defined flows are merged |
| shibboleth.InterceptFlow | ProfileInterceptorFlowDescriptor | Abstract parent bean for defining new flow descriptor beans |
Notes
TBD