...
The SP supports the following rule "types" (the type is the first parameter of the command):
Rule | Apache Version | Details |
---|---|---|
shibboleth | This is a special "dummy" rule that allows a | |
shib-session | 2.4 and Later OR ShibCompatWith24 | A rule that requires an authenticated session, but nothing else. No information of any kind about the user is required in order to satisfy this rule and it should never be used in the absence of additional application logic to perform authorization. This is equivalent to when ShibCompatValidUser is Off |
shib-user | 2.4 and Later OR ShibCompatWith24 | A rule based on the REMOTE_USER value established for the request. The remaining parameters are the values to compare against. Regular expression and negation modifiers are supported (see below). |
group | 2.2 and Earlier | A rule to check membership of the REMOTE_USER value established for the request against a group membership file designated with the AuthGroupFile command. The remaining parameters are the names of groups to check membership against. Starting with Apache 2.4, support for this option is left up to other "out of the box" Apache module support for group-based rules, rather than reimplemented by the SP |
authnContextClassRef | A rule based on the SAML authentication context class or method asserted by the IdP. The remaining parameters are the values to compare against. | |
authnContextDeclRef | A rule based on the SAML authentication context declaration asserted by the IdP. The remaining parameters are the values to compare against. | |
shib-plugin | 2.4 and Later OR ShibCompatWith24 | Enables the use of XML Access Control rules for access control. The single parameter is the path to an access control configuration file. The plug-in is loaded on every request, which allows on-the-fly changes of access control rules (though is less efficient if large rulesets are used). This is equivalent to the older ShibAccessControl option and can be enabled for use with older Apache versions using the ShibCompatWith24 option. |
shib-attr | 2.4 and Later OR ShibCompatWith24 | The Apache 2.4 authorization API does not allow for "extensible" rule types within a single module, so to accomodate rules based on attributes, a new rule type is used. The first parameter to the rule specifies the attribute ID to check, and the rest of the parameters are used as values to check for. This rule type can be enabled for use with older Apache versions using the |
Rule Modifiers
Two rule modifiers are supported to affect the processing of the rule types that accept parameters (all but the first two above). Modifiers are placed after the rule type but before any comparison values
Modified | Details |
---|---|
~ (tilde) | The tilde modifier causes the rest of the parameters to be interpreted as regular expressions rather than literal values. The |
! (bang) | The bang modifier inverts the rule such that a non-match satisfies the rule. This does not apply to rules based on arbitrary attributes (the ones identified by an arbitrary string). |
The two modifiers can be combined, so as to enforce a regular expression that must NOT match. When using both modifiers, be sure to separate them with a space (see examples).
...
To control this behavior, the AuthzShibAuthoritative
command is supplied. The following matrix describes how the options interact when an unrecogized rule is found:
|
| |
---|---|---|
| Access Denied | Decision Left to Other Modules |
| Ignored | Ignored |
Recommended Practices for Compatibility
...
The soonest changes would be made to remove deprecated options is in a V3V4.0 release of the SP, and there are no current plans for that. However the various combinations and issues are quite complex due to the software's age, so avoiding all of this is the best option.
Examples
...