basic:Script prior to V3.2) type allows definition of complex filtering with a scriptlet as either a Mapper or a PolicyRule depending on the location. The script is either a Policy Rule or a Mapper depending on its location:
- If the script is specified within the scope of an
<AttributeRule>element then the script has to be Mapper, returning a
Set<IdPAttributeValue>, which is added to the permit or deny list for the attribute in question.
- If the script is specified within the scope of a
<PolicyRequirementRule>element then the script has to be a PolicyRule (returning a
Boolean), which defines whether the rule is active or not.
Script type is defined in the
namespace, the schema for which can be located at http://shibboleth.net/schema/idp/shibboleth-afp.xsd
basic: type was defined in the
namespace, the schema for which can be located at http://shibboleth.net/schema/idp/shibboleth-afp-mf-basic.xsd
Two optional attributes may be specified:
The language of the script
|String||The name of a Spring Bean defined elsewhere. This bean will be made available to the script with the name "|
One of two child elements can be provided
|The path of a resource (usually a file) which contains the script|
|The script. It is usual to specify this within a CDATA|
Data available to the script
The script has the following variables available
|AttributeFilterContext||The AttributeFilter context provides some information about the request, and a mechanism to navigate to other contexts in the tree|
The root context for the request
The attribute being filtered
|Object||Contains whatever was provided by the |
Array of Subject
|The Subjects associated with this authorization. Note that these will only be present if the attribute resolution has been associated with an Authentication (and so this will not work for back channel requests).|
This simple rule just adds the first value of the attribute "email" to its permit list.
No compatibility with V2 is provided..