...
Internally, the following beans are defined as with default configurations of the supported login flowsc14n methods:
All Most of these methods are predominantly expected to be configured by means of method-specific properties in conf/c14n/subject-c14n.properties, as discussed on those pages. In a few cases, there are still additional Spring beans used, as noted on each of their documentation pages.
To use one or more of these c14n methods with a particular login flow, you define a property specific to that login flow in conf/authn/authn.properties (they are present but commented in the latest “shipping” default version of that file). These properties are contain a comma-delimited list of c14n bean IDs to attempt for each login flow.
...
In this manner, each login method is can be explicitly configured to run the methods c14n logic required without any concern about overlap.
Older Plugins
With IdP plugins targeted at V5.0 and V5.1, the property based approach described above is not supported yet, and so you will need to refer to the older documentation and leverage the legacy list bean to configure c14n. When in doubt, refer to the plugin’s documentation on that.
Advanced Topics
Multiple Instances of a Method
It is now possible to configure multiple copies of a particular c14n method with different settings. This requires additional Spring XML configuration since the default instances get most of their behavior from a single set of properties. The attribute-sourced method is the most common use case for this, since its configuration includes the specification of which attribute(s) to resolve and source from, and the mechanism that method also doubles as a means of extracting a username from incoming data when proxying to another IdP.
...