Fediz Plugin configuration
This page describes the Fediz configuration file referenced by the security interceptor of the Servlet Container (eg. authenticator in Tomcat/Jetty).
The Fediz configuration information is used to publish the federation Metadata document which is described here
The following example shows the minimum configuration for Fediz.
The protocol element declares that the WS-Federation protocol is being used. The issuer element shows the URL to which authenticated requests will be redirected with a SignIn request.
The IDP issues a SAML token which must be validated by the plugin. The validation requires the certificate store of the Certificate Authority(ies) of the certificate which signed the SAML token. This is defined in
certificateStore. The signing certificate itself is not required because
certificateValidation is set to
subject defines the trusted signing certificate using the subject as a regular expression.
Finally, the audience URI is validated against the audience restriction in the SAML token.
The values of the list of audience URIs are verified against the element
AudienceRestriction in the SAML token
Trusted certificate store
The list of keystores (JKS, PEM) includes at least the certificate of the Certificate Authorities (CA) which signed the certificate which is used to sign the SAML token.
If the file location is not fully qualified it needs to be relative to the Container home directory
There are two ways to configure a trusted issuer (IDP). Either you configure the subject name and the CA(s) who signed the certificate of the IDP (
certificateValidation=ChainTrust) or you configure the certificate of the IDP and the CA(s) who signed it (
Maximum Clock Skew
Maximum allowable time difference between the system clocks of the IDP and RP.
Default 5 seconds.
Token Replay Cache
The TokenReplayCache implementation to use to cache tokens. The default is an implementation based on EHCache.
Key for Signature
If configured, the published (WS-Federation) Metadata document is signed by this key. Otherwise, not signed.
A Keystore used to decrypt an encrypted token.
WS-Federation protocol configuration reference
This URL defines the location of the IDP to whom unauthenticated requests are redirected
Security realm of the Relying Party / Application. This value is part of the SignIn request as the
Default: URL including the Servlet Context
The authentication type defines what kind of authentication is required. This information is provided in the SignInRequest to the IDP (parameter
The WS-Federation standard defines a list of predefined URIs for wauth here.
Role Claim URI
Defines the attribute name of the SAML token which contains the roles.
Required for Role Based Access Control.
Role Value Delimiter
There are different ways to encode multi value attributes in SAML.
- Single attribute with multiple values
- Several attributes with the same name but only one value
- Single attribute with single value. Roles are delimited by
The claims required by the Relying Party are listed here. Claims can be optional. If a mandatory claim can't be provided by the IDP the issuance of the token should fail
Indicates the Resource IDP the home realm of the requestor. This may be an URL or an identifier like urn: or uuid: and depends on the Resource IDP implementation. This value is part of the SignIn request as the
The desired "freshness" of the token from the IdP. This information is provided in the SignInRequest to the IdP (parameter
|request||Request||Optional||NA||This value is part of the SignIn request as the wreq parameter. It can be used to specify a desired TokenType from the IdP.|
Custom Token validator classes can be configured here. The SAML Token validator is enabled by default.
See example here
Attributes resolved at runtime
The following attributes can be either configured statically at deployment time or dynamically when the initial request is received:
These configuration elements allows for configuring a CallbackHandler which gets a Callback object where the appropriate value must be set. The CallbackHandler implementation has access to the HttpServletRequest. The XML attribute
type must be set to
For more information see Fediz Extensions.
The following example defines the required claims and configures a custom callback handler to define some configuration values at runtime.