type="XML", this AttributeFilter implements an XML-based rule syntax for filtering attributes that was forked off from the original filtering language that was designed for the V2 IdP software. The best link to it for the moment is to the old docs because the V3 language has significantly drifted.
This filter's configuration is implemented as a reloadable XML resource, which means that the XML content can be supplied inline, in a local file, or a remote file, and can be monitored for changes and reloaded on the fly. The root of the XML in any of those cases MUST be an
<afp:AttributeFilterPolicyGroup> element, either as a child element in an existing file or the root of a different file (usually the latter).
Not a lot, this continues to point back to the old V2 IdP software docs for the moment. The main point of divergence with the V3 IdP is the collapsing of namespaces and shortening of some of the function plugin names, which was not backported to the SP.
This page refers to several different namespaces by convention as detailed below:
|The Shibboleth attribute filter rules namespace|
|The "basic" Shibboleth attribute filter rules namespace|
|The "SAML" attribute filter rules namespace|
|The Shibboleth SP configuration namespace|
Aside from the
type="XML" attribute itself, there is no other attribute content specific to this plugin type.
It supports all of the attributes common to all reloadable configuration resources:
|string||Identifies the component for logging purposes.|
Remote location of an XML resource containing the required configuration. The SP does not verify the transport (i.e. it does not verify the X.509 certificate presented by the remote server when HTTPS is the transport).
Path to a local file containing the required configuration
|boolean||false||If true, XML validation is performed when loading the resource|
|boolean||true||If a |
|time in seconds||0||If a |
|local path||If a |
|local path||Path to a certificate containing a public key to use to require and verify an XML signature over the resource. The certificate's other content is ignored.|
|string||If present, the name is supplied to the |
The following child element must be provided, either inline, or as the root element of a local or remote XML resource to load from, which would be specified via the attribute(s) above.
|1||Root element of configuration|
When a non-inline configuration is used, it supports the following child elements common to all reloadable configuration resources.
These child elements are typically only used when relying on a remote configuration resource and are for advanced use cases.
|0 or 1||Used to require the presence of a top-level signature over the entire resource and to control the verification process|
|0 or 1|
Used to require the presence of a top-level signature over the entire resource and to control the verification process.
Mutually exclusive with the
|0 or more||Provides low-level control over the library used to remotely access the resource|
The best example to this point is the file shipped with the software.