Apendix - Howto: Create a virtual platform Shibboleth

7. Apendix

IDP: httpd.conf

AuthType Basic

AuthName "My Identity Provider"

AuthUserFile /usr/local/idp/credentials/user.db require valid-user

</Location>

ProxyPass /idp/ ajp://127.0.0.1:8009/idp/

ProxyPass /jsp-examples/ ajp://127.0.0.1:8009/jsp-examples/

SSLCertificateFile /usr/local/idp/credentials/idp.crt SSLCertificateKeyFile /usr/local/idp/credentials/idp.key SSLVerifyClient optional_no_ca

SSLVerifyDepth 10

Loggers define indicate which packages/categories are logged, at which level, and to which appender.

Levels: OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL -->

</logger>

</logger>

</logger>

</logger>

<!--

Normally you should not edit below this point. These default configurations are sufficient for

almost every system.

-->

<!--

Logging appenders define where and how logging messages are logged.

-->

<appender name="IDP_ACCESS"

class="ch.qos.logback.core.rolling.RollingFileAppender">

<File>/usr/local/idp/logs/idp-access.log</File>

<FileNamePattern>/usr/local/idp/logs/idp-access-%d{yyyy-MM-dd}.log</FileNamePattern>

</rollingPolicy>

</layout>

</appender>

<appender name="IDP_AUDIT"

class="ch.qos.logback.core.rolling.RollingFileAppender">

<File>/usr/local/idp/logs/idp-audit.log</File>

<FileNamePattern>/usr/local/idp/logs/idp-audit-%d{yyyy-MM-dd}.log</FileNamePattern>

</rollingPolicy>

</layout>

</appender>

<appender name="IDP_PROCESS"

class="ch.qos.logback.core.rolling.RollingFileAppender">

<File>/usr/local/idp/logs/idp-process.log</File>

<!--

-->

<FileNamePattern>/usr/local/idp/logs/idp-process-%d{yyyy-MM-dd}.log</FileNamePattern>

</rollingPolicy>

-->

</layout>

</appender>

<appender-ref ref="IDP_ACCESS" />

</logger>

<appender-ref ref="IDP_AUDIT" />

</logger>

</logger>

</logger>

<root>

<appender-ref ref="IDP_PROCESS" />

</root>

</configuration>

IDP: ports.conf

# If you just change the port or add more ports here, you will likely also

# have to change the VirtualHost statement in

# /etc/apache2/sites-enabled/000-default

# This is also true if you have upgraded from before 2.2.9-3 (i.e. from

# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and

# README.Debian.gz

NameVirtualHost *:80 Listen 80

# SSL name based virtual hosts are not yet supported, therefore no # NameVirtualHost statement here

Listen 8443 Listen 443

</IfModule>

IDP: relying-party.xml

<?xml version="1.0" encoding="UTF-8"?>

<!--

This file is an EXAMPLE configuration file.

This file specifies relying party dependent configurations for the IdP, for example, whether SAML assertions to a

particular relying party should be signed. It also includes metadata provider and credential definitions used

when answering requests to a relying party.

-->

<AnonymousRelyingParty provider="https://192.168.0.1/idp/shibboleth"

defaultSigningCredentialRef="IdPCredential" />

<DefaultRelyingParty provider="https://192.168.0.1/idp/shibboleth"

defaultSigningCredentialRef="IdPCredential">

-->

<ProfileConfiguration xsi:type="saml:ShibbolethSSOProfile"

includeAttributeStatement="false"

assertionLifetime="300000"

signResponses="always"

signAssertions="always" />

<ProfileConfiguration xsi:type="saml:SAML1AttributeQueryProfile"

assertionLifetime="300000"

signResponses="conditional"

signAssertions="never" />

<ProfileConfiguration xsi:type="saml:SAML1ArtifactResolutionProfile"

signResponses="conditional"

signAssertions="never" />

<ProfileConfiguration xsi:type="saml:SAML2SSOProfile"

includeAttributeStatement="true"

<ProfileConfiguration xsi:type="saml:SAML2AttributeQueryProfile"

assertionLifetime="300000"

<ProfileConfiguration xsi:type="saml:SAML2ArtifactResolutionProfile"

signResponses="conditional"

signAssertions="never"

encryptAssertions="conditional"

encryptNameIds="never"/>

</DefaultRelyingParty>

<MetadataProvider id="ShibbolethMetadata" xsi:type="ChainingMetadataProvider"

xmlns="urn:mace:shibboleth:2.0:metadata">

<MetadataProvider id="IdPMD" xsi:type="ResourceBackedMetadataProvider"

xmlns="urn:mace:shibboleth:2.0:metadata" >

<MetadataResource xsi:type="resource:FilesystemResource"

file="/usr/local/idp/metadata/idp-metadata.xml" />

</MetadataProvider>

<!--

<MetadataProvider id="URLMD" xsi:type="FileBackedHTTPMetadataProvider"

xmlns="urn:mace:shibboleth:2.0:metadata"

<MetadataFilter xsi:type="EntityRoleWhiteList"

xmlns="urn:mace:shibboleth:2.0:metadata">

</MetadataProvider>

<security:Credential id="IdPCredential" xsi:type="security:X509Filesystem">

<security:PrivateKey>/usr/local/idp/credentials/idp.key</security:PrivateKey>

<security:Certificate>/usr/local/idp/credentials/idp.crt</security:Certificate>

</security:Credential>

<!--

<security:TrustEngine id="shibboleth.MetadataTrustEngine"

xsi:type="security:StaticExplicitKeySignature">

<security:Credential id="MyFederation1Credentials"

xsi:type="security:X509Filesystem">

<security:Certificate>/usr/local/idp/credentials/federation1.crt</security:Certificate>

</security:Credential>

</security:TrustEngine>

-->

<!--

The following trust engines and rules control every aspect of security related to incoming messages.

Trust engines evaluate various tokens (like digital signatures) for trust worthiness while the

security policies establish a set of checks that an incoming message must pass in order to be considered

secure. Naturally some of these checks require the validation of the tokens evaluated by the trust

engines and so you'll see some rules that reference the declared trust engines.

-->

<security:TrustEngine id="shibboleth.SignatureTrustEngine"

xsi:type="security:SignatureChaining">

<security:TrustEngine id="shibboleth.SignatureMetadataExplicitKeyTrustEngine"

xsi:type="security:MetadataExplicitKeySignature"

metadataProviderRef="ShibbolethMetadata" />

<security:TrustEngine id="shibboleth.SignatureMetadataPKIXTrustEngine"

xsi:type="security:MetadataPKIXSignature"

metadataProviderRef="ShibbolethMetadata" />

</security:TrustEngine>

<security:TrustEngine id="shibboleth.CredentialTrustEngine"

xsi:type="security:Chaining">

<security:TrustEngine id="shibboleth.CredentialMetadataExplictKeyTrustEngine"

xsi:type="security:MetadataExplicitKey"

metadataProviderRef="ShibbolethMetadata" />

<security:TrustEngine id="shibboleth.CredentialMetadataPKIXTrustEngine"

xsi:type="security:MetadataPKIXX509Credential"

metadataProviderRef="ShibbolethMetadata" />

</security:TrustEngine>

<security:SecurityPolicy id="shibboleth.ShibbolethSSOSecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:IssueInstant" required="false"/>

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

</security:SecurityPolicy>

<security:SecurityPolicy id="shibboleth.SAML1AttributeQuerySecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:Replay"/>

<security:Rule xsi:type="samlsec:IssueInstant"/>

<security:Rule xsi:type="samlsec:ProtocolWithXMLSignature"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="security:ClientCertAuth"

trustEngineRef="shibboleth.CredentialTrustEngine" />

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

<security:Rule xsi:type="security:MandatoryMessageAuthentication" />

</security:SecurityPolicy>

<security:SecurityPolicy id="shibboleth.SAML1ArtifactResolutionSecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:Replay"/>

<security:Rule xsi:type="samlsec:IssueInstant"/>

<security:Rule xsi:type="samlsec:ProtocolWithXMLSignature"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="security:ClientCertAuth"

trustEngineRef="shibboleth.CredentialTrustEngine" />

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

<security:Rule xsi:type="security:MandatoryMessageAuthentication" />

</security:SecurityPolicy>

<security:SecurityPolicy id="shibboleth.SAML2SSOSecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:Replay"/>

<security:Rule xsi:type="samlsec:IssueInstant"/>

<security:Rule xsi:type="samlsec:SAML2AuthnRequestsSigned"/>

<security:Rule xsi:type="samlsec:ProtocolWithXMLSignature"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPRedirectSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPPostSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

</security:SecurityPolicy>

<security:SecurityPolicy id="shibboleth.SAML2AttributeQuerySecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:Replay"/>

<security:Rule xsi:type="samlsec:IssueInstant"/>

<security:Rule xsi:type="samlsec:ProtocolWithXMLSignature"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPRedirectSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPPostSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="security:ClientCertAuth"

trustEngineRef="shibboleth.CredentialTrustEngine" />

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

<security:Rule xsi:type="security:MandatoryMessageAuthentication" />

</security:SecurityPolicy>

<security:SecurityPolicy id="shibboleth.SAML2ArtifactResolutionSecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:Replay"/>

<security:Rule xsi:type="samlsec:IssueInstant"/>

<security:Rule xsi:type="samlsec:ProtocolWithXMLSignature"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPRedirectSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPPostSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="security:ClientCertAuth"

trustEngineRef="shibboleth.CredentialTrustEngine" />

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

<security:Rule xsi:type="security:MandatoryMessageAuthentication" />

</security:SecurityPolicy>

<security:SecurityPolicy id="shibboleth.SAML2SLOSecurityPolicy"

xsi:type="security:SecurityPolicyType">

<security:Rule xsi:type="samlsec:Replay"/>

<security:Rule xsi:type="samlsec:IssueInstant"/>

<security:Rule xsi:type="samlsec:ProtocolWithXMLSignature"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPRedirectSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="samlsec:SAML2HTTPPostSimpleSign"

trustEngineRef="shibboleth.SignatureTrustEngine" />

<security:Rule xsi:type="security:ClientCertAuth"

trustEngineRef="shibboleth.CredentialTrustEngine" />

<security:Rule xsi:type="samlsec:MandatoryIssuer"/>

<security:Rule xsi:type="security:MandatoryMessageAuthentication" />

</security:SecurityPolicy>

</RelyingPartyGroup>

Options Indexes FollowSymLinks MultiViews AllowOverride None

Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny

Allow from all

</Directory>

ErrorLog /var/log/apache2/error.log

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

LogLevel warn

CustomLog /var/log/apache2/ssl_access.log combined

Alias /doc/ "/usr/share/doc/"

Options Indexes MultiViews FollowSymLinks AllowOverride None

Order deny,allow Deny from all

Allow from 127.0.0.0/255.0.0.0 ::1/128

</Directory>

# SSL Engine Switch:

# Enable/Disable SSL for this virtual host.

SSLEngine on

# A self-signed (snakeoil) certificate can be created by installing

# the ssl-cert package. See

# /usr/share/doc/apache2.2-common/README.Debian.gz for more info.

# If both key and certificate are stored in the same file, only the

# SSLCertificateFile directive is needed.

#SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem

#SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

# Server Certificate Chain:

# Point SSLCertificateChainFile at a file containing the

# concatenation of PEM encoded CA certificates which form the

# certificate chain for the server certificate. Alternatively

# the referenced file can be the same as SSLCertificateFile

# when the CA certificates are directly appended to the server

# certificate for convinience.

#SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

# Certificate Authority (CA):

# Set the CA certificate verification path where to find CA

# certificates for client authentication or alternatively one

# huge file containing all of them (file must be PEM encoded)

# Note: Inside SSLCACertificatePath you need hash symlinks

# to point to the certificate files. Use the provided

# Makefile to update the hash symlinks after changes.

#SSLCACertificatePath /etc/ssl/certs/

#SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

# Certificate Revocation Lists (CRL):

# Set the CA revocation path where to find CA CRLs for client

# authentication or alternatively one huge file containing all

# of them (file must be PEM encoded)

# Note: Inside SSLCARevocationPath you need hash symlinks

# to point to the certificate files. Use the provided

# Makefile to update the hash symlinks after changes.

#SSLCARevocationPath /etc/apache2/ssl.crl/

#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

# Client Authentication (Type):

# Client certificate verification type and depth. Types are

# none, optional, require and optional_no_ca. Depth is a

# number which specifies how deeply to verify the certificate

# issuer chain before deciding the certificate is not valid.

#SSLVerifyClient require

#SSLVerifyDepth 10

# Access Control:

# With SSLRequire you can do per-directory access control based

# on arbitrary complex boolean expressions containing server

# variable checks and other lookup directives. The syntax is a

# mixture between C and Perl. See the mod_ssl documentation

# for more details.

#<Location />

#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \

# Translate the client X.509 into a Basic Authorisation. This means that

# the standard Auth/DBMAuth methods can be used for access control. The

# user name is the `one line' version of the client's X.509 certificate.

# Note that no password is obtained from the user. Every entry in the user

# file needs this password: `xxj31ZMTZzkVA'.

# o ExportCertData:

# This exports two additional environment variables: SSL_CLIENT_CERT and

# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the

# server (always existing) and the client (only existing when client

# authentication is used). This can be used to import the certificates

# into CGI scripts.

# o StdEnvVars:

# This exports the standard SSL/TLS related `SSL_*' environment variables.

# Per default this exportation is switched off for performance reasons,

# because the extraction step is an expensive operation and is usually

# useless for serving static content. So one usually enables the

# exportation for CGI and SSI requests only.

# o StrictRequire:

# This denies access when "SSLRequireSSL" or "SSLRequire" applied even

# under a "Satisfy any" situation, i.e. when it applies access is denied

# and no other module can change it.

# o OptRenegotiate:

# This enables optimized SSL connection renegotiation handling when SSL

# directives are used in per-directory context.

#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire

# SSL Protocol Adjustments:

# The safe and default but still SSL/TLS standard compliant shutdown

# approach is that mod_ssl sends the close notify alert but doesn't wait for

# the close notify alert from client. When you need a different shutdown

# approach you can use one of the following variables:

# o ssl-unclean-shutdown:

# This forces an unclean shutdown when the connection is closed, i.e. no

# SSL close notify alert is send or allowed to received. This violates

# the SSL/TLS standard but is needed for some brain-dead browsers. Use

# this when you receive I/O errors because of the standard approach where

# mod_ssl sends the close notify alert.

# o ssl-accurate-shutdown:

# This forces an accurate shutdown when the connection is closed, i.e. a

# SSL close notify alert is send and mod_ssl waits for the close notify

# alert of the client. This is 100% SSL/TLS standard compliant, but in

# practice often causes hanging connections with brain-dead browsers. Use

# this only for browsers where you know that their SSL implementation

# works correctly.

# Notice: Most problems of broken clients are also related to the HTTP

# keep-alive facility, so you usually additionally want to disable

# keep-alive for those clients, too. Use variable "nokeepalive" for this.

# Similarly, one has to force some clients to use HTTP/1.0 to workaround

# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and

# "force-response-1.0" for this.

BrowserMatch ".*MSIE.*" \

nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0

</VirtualHost>

</IfModule>

Location="https://192.168.0.1/idp/profile/SAML2/Redirect/SSO"/></IDPSSODescriptor><At tributeAuthorityDescriptor

protocolSupportEnumeration="urn:oasis:names:tc:SAML:1.1:protocol urn:oasis:names:tc:SAML:2.0:protocol"><Extensions><shibmd:Scope

regexp="false">0.1</shibmd:Scope></Extensions><KeyDescriptor><ds:KeyInfo><ds:X509 Data><ds:X509Certificate>MIIDFzCCAf+gAwIBAgIUJFoRhZM+TMUKaqRoRJ4vUHRyV gowDQYJKoZIhvcNAQEF

BQAwFjEUMBIGA1UEAxMLMTkyLjE2OC4wLjEwHhcNMDkxMTIzMTU0NTE1WhcN Mjkx

MTIzMTU0NTE1WjAWMRQwEgYDVQQDEwsxOTIuMTY4LjAuMTCCASIwDQYJKoZ IhvcN

AQEBBQADggEPADCCAQoCggEBALZhnktNTzAk3Ax5hw0bjZwntnZkD/bUWGQZ691r Cuh6MKnamkmDt1mYN47LET4iZD/EkSwNI6G6ZeoboRAAA2J1vutyYmJasyWK1eyH pd8wjFbWUQWwK3BpNJQC6dOa6MAmI/BdiVKq1ckhC6pyipYLhi110KYc9YrMtog0 msUHUe5L7MSdwdwW3jgJUjgMyslUp1tE0n4wXnEmF+z9GxgVnFeGXU4KSH/kbeUm xC9w6PrSW9tkOPuIv2QvnHch0LeB7fMdpF73TsYZd4gsEZdZpamW8ZPN5NMK1gEJ lHYfHaHWISAk7FFaEU+75qkjTtEsU7Sh2dkwqqAbGtd7bdECAwEAAaNdMFswOgYD VR0RBDMwMYILMTkyLjE2OC4wLjGGImh0dHBzOi8vMTkyLjE2OC4wLjEvaWRwL3N o

aWJib2xldGgwHQYDVR0OBBYEFL0mWrs/k409iTLIqpJr+Ndaa45LMA0GCSqGSIb3 DQEBBQUAA4IBAQCeyDO6S+sHEt7iXuAnmndIKa4BgKHePl01ePdE4PyNx0qqH/E0 fwnHTo1M/itlRn5M9heFuwfnXiMYeXjGg6eBx7+AUNFP4/b+/vbuuWolA/y4nhVF 6tBwLKpQZIkupfqfBdx7d9MbWVQ9oxleScWzZyVc3j/rriqqTKi8BHoUrm2bd+gj /IgYFZSi0ESbPkf5pLhAxFeZQpWxwZ6QqdnJsiVaaHvSh6Bha6etxTjbN5NOpQFh RxlXrOxY2/6U0fyNPsAXr65RYS2Mt8uH618tm3hqjUnpSvfxp0O8fsnQZGAvsWmd XUrfThTGvZjng82kzzCGYXQguy/t7Pa3rsRl</ds:X509Certificate></ds:X509Data></ds:Ke yInfo></KeyDescriptor><AttributeService

Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding"

Location="https://192.168.0.1:8443/idp/profile/SAML1/SOAP/AttributeQuery"/><AttributeS ervice Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"

Location="https://192.168.0.1:8443/idp/profile/SAML2/SOAP/AttributeQuery"/><NameIDF ormat>urn:mace:shibboleth:1.0:nameIdentifier</NameIDFormat><NameIDFormat>urn:oasis

:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat></AttributeAuthorityDescriptor></EntityDescriptor>

SP: httpd.conf UseCanonicalName On

# RPM installations on platforms with a conf.d directory will

# result in this file being copied into that directory for you.

# For non-RPM installs, you can add this file to your

# configuration using an Include command in httpd.conf

######

## SHIB Config

######

# Load the SHIBBOLETH module

LoadModule mod_shib /usr/lib/apache2/modules/mod_shib_22.so

# Used for example logo and style sheet in error templates.

Allow from all </Location>

Alias /shibboleth-sp/main.css /usr/share/shibboleth/main.css Alias /shibboleth-sp/logo.jpg /usr/share/shibboleth/logo.jpg

</IfModule>

# Configure the module for content

# You can now do most of this in shibboleth.xml using the RequestMap

In document Howto: Create a virtual platform Shibboleth (Page 15-46)