Under construction
Fediz Plugin configuration
This page describes the Fediz configuration file referenced by the security interceptor (eg. authenticator in Tomcat/Jetty).
Example
The following example shows the minimum configuration for Fediz.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <FedizConfig> <contextConfig name="/fedizhelloworld"> <audienceUris> <audienceItem>https://localhost:8443/fedizhelloworld</audienceItem> </audienceUris> <certificateStores> <trustManager> <keyStore file="conf/stsstore.jks" password="stsspass" type="JKS" /> </trustManager> </certificateStores> <trustedIssuers> <issuer name="issuer 1" certificateValidation="ChainTrust" subject=".*CN=www.sts.com.*" /> </trustedIssuers> <protocol xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="federationProtocolType" version="1.2"> <issuer>https://localhost:9443/fedizidp/</issuer> </protocol> </contextConfig> </FedizConfig>
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 ChainTrust
. The 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.
Configuration reference
XML element |
Name |
Use |
Description |
---|---|---|---|
audienceUris |
Audience URI |
Required |
The values of the list of audience URIs are verified against the element |
certificateStores |
Trusted certificate store |
Required |
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. |
trustedIssuers |
Trusted Issuers |
Required |
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 ( |
maximumClockSkew |
Maximum Clock Skew |
Optional |
Maximum allowable time difference between the system clocks of the IDP and RP. |
WS-Federation protocol configuration reference
XML element |
Name |
Use |
Description |
---|---|---|---|
issuer |
Issuer URL |
Required |
This URL defines the location of the IDP to whom unauthenticated requests are redirected |
realm |
Realm |
Optional |
Security realm of the Relying Party / Application. This value is part of the SignIn request as the |
authenticationType |
Authentication Type |
Optional |
The authentication type defines what kind of authentication is required. This information is provided in the SignInRequest to the IDP (parameter |
roleURI |
Role Claim URI |
Optional |
Defines the attribute name of the SAML token which contains the roles |
roleDelimiter |
Role Value Delimiter |
Optional |
There are different ways to encode multi value attributes in SAML.
|
claimTypesRequested |
Requested claims |
Optional |
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 |
homeRealm |
Home Realm |
Optional |
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 |
Attributes resolved at runtime
The following attributes can be either configured statically at deployment time or dynamically when the initial request is received:
- authenticationType
- homeRealm
- issuer
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 Class
.
Advanced example
The following example defines the required claims and configures a custom callback handler to define some configuration values at runtime.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <FedizConfig> <contextConfig name="/fedizhelloworld"> <audienceUris> <audienceItem>https://localhost:8443/fedizhelloworld</audienceItem> </audienceUris> <certificateStores> <keyStore file="conf/stsstore.jks" password="stsspass" type="file" /> </certificateStores> <maximumClockSkew>10</maximumClockSkew> <trustedIssuers> <issuer name="issuer 1" certificateValidation="ChainTrust" subject=".*CN=www.sts.com.*" /> </trustedIssuers> <protocol xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="federationProtocolType" version="1.2"> <issuer>https://localhost:9443/fedizidp/</issuer> <roleDelimiter>,</roleDelimiter> <roleURI>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/role</roleURI> <claimTypesRequested> <claimType type="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/role" optional="true" /> </claimTypesRequested> <authenticationType type="String" value="http://docs.oasis-open.org/wsfed/authorization/200706/authntypes/smartcard" /> <homeRealm type="Class" value="example.HomeRealmCallbackHandler" /> </protocol> </contextConfig> </FedizConfig>