Author: buildbot
Date: Tue Nov 5 14:48:00 2013
New Revision: 885519
Log:
Production update by buildbot for cxf
Added:
websites/production/cxf/content/fediz-idp-11.html
Modified:
websites/production/cxf/content/cache/main.pageCache
Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Added: websites/production/cxf/content/fediz-idp-11.html
==============================================================================
--- websites/production/cxf/content/fediz-idp-11.html (added)
+++ websites/production/cxf/content/fediz-idp-11.html Tue Nov 5 14:48:00 2013
@@ -0,0 +1,501 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<html>
+ <head>
+
+<link type="text/css" rel="stylesheet" href="/resources/site.css">
+<script src='/resources/space.js'></script>
+
+<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
+<meta name="keywords" content="business integration, EAI, SOA, Service
Oriented Architecture, web services, SOAP, JBI, JMS, WSDL, XML, EDI, Electronic
Data Interchange, standards support, integration standards, application
integration, middleware, software, solutions, services, CXF, open source">
+<meta name="description" content="Apache CXF, Services Framework - Fediz IDP
1.1">
+
+
+<link type="text/css" rel="stylesheet"
href="/resources/highlighter/styles/shCoreCXF.css">
+<link type="text/css" rel="stylesheet"
href="/resources/highlighter/styles/shThemeCXF.css">
+
+<script src='/resources/highlighter/scripts/shCore.js'></script>
+<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
+<script>
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+</script>
+
+
+ <title>
+Apache CXF -- Fediz IDP 1.1
+ </title>
+ </head>
+<body onload="init()">
+
+
+<table width="100%" cellpadding="0" cellspacing="0">
+ <tr>
+ <td id="cell-0-0" colspan="2"> </td>
+ <td id="cell-0-1"> </td>
+ <td id="cell-0-2" colspan="2"> </td>
+ </tr>
+ <tr>
+ <td id="cell-1-0"> </td>
+ <td id="cell-1-1"> </td>
+ <td id="cell-1-2">
+ <!-- Banner -->
+<div class="banner" id="banner"><div><table border="0" cellpadding="0"
cellspacing="0" width="100%"><tr><td align="left" colspan="1" nowrap>
+<a shape="rect" href="http://cxf.apache.org/"; title="Apache CXF"><span
style="font-weight: bold; font-size: 170%; color: white">Apache CXF</span></a>
+</td><td align="right" colspan="1" nowrap>
+<a shape="rect" href="http://www.apache.org/"; title="The Apache Software
Foundation"><img border="0" alt="ASF Logo"
src="http://cxf.apache.org/images/asf-logo.png";></a>
+</td></tr></table></div></div>
+ <!-- Banner -->
+ <div id="top-menu">
+ <table border="0" cellpadding="1" cellspacing="0" width="100%">
+ <tr>
+ <td>
+ <div align="left">
+ <!-- Breadcrumbs -->
+<a href="index.html">Index</a> > <a
href="fediz.html">Fediz</a> > <a href="fediz-idp-11.html">Fediz
IDP 1.1</a>
+ <!-- Breadcrumbs -->
+ </div>
+ </td>
+ <td>
+ <div align="right">
+ <!-- Quicklinks -->
+<div id="quicklinks"><p><a shape="rect" href="download.html"
title="Download">Download</a> | <a shape="rect"
href="http://cxf.apache.org/docs/index.html";>Documentation</a></p></div>
+ <!-- Quicklinks -->
+ </div>
+ </td>
+ </tr>
+ </table>
+ </div>
+ </td>
+ <td id="cell-1-3"> </td>
+ <td id="cell-1-4"> </td>
+ </tr>
+ <tr>
+ <td id="cell-2-0" colspan="2"> </td>
+ <td id="cell-2-1">
+ <table>
+ <tr valign="top">
+ <td height="100%">
+ <div id="wrapper-menu-page-right">
+ <div id="wrapper-menu-page-top">
+ <div id="wrapper-menu-page-bottom">
+ <div id="menu-page">
+ <!-- NavigationBar -->
+<div id="navigation"><h3><a shape="rect"
name="Navigation-ApacheCXFIndex"></a><a shape="rect" href="index.html"
title="Index">Apache CXF</a></h3>
+
+<ul class="alternate" type="square"><li><a shape="rect" href="index.html"
title="Index">Home</a></li><li><a shape="rect" href="download.html"
title="Download">Download</a></li><li><a shape="rect" href="people.html"
title="People">People</a></li><li><a shape="rect" href="project-status.html"
title="Project Status">Project Status</a></li><li><a shape="rect"
href="roadmap.html" title="Roadmap">Roadmap</a></li><li><a shape="rect"
href="mailing-lists.html" title="Mailing Lists">Mailing Lists</a></li><li><a
shape="rect" class="external-link"
href="http://issues.apache.org/jira/browse/CXF";>Issue Reporting</a></li><li><a
shape="rect" href="special-thanks.html" title="Special Thanks">Special
Thanks</a></li><li><a shape="rect" class="external-link"
href="http://www.apache.org/licenses/";>License</a></li><li><a shape="rect"
href="security-advisories.html" title="Security Advisories">Security
Advisories</a></li></ul>
+
+
+<h3><a shape="rect" name="Navigation-Users"></a>Users</h3>
+
+<ul class="alternate" type="square"><li><a shape="rect"
href="http://cxf.apache.org/docs/index.html";>User's Guide</a></li><li><a
shape="rect" href="support.html" title="Support">Support</a></li><li><a
shape="rect" href="faq.html" title="FAQ">FAQ</a></li><li><a shape="rect"
href="resources-and-articles.html" title="Resources and Articles">Resources and
Articles</a></li></ul>
+
+
+<h3><a shape="rect" name="Navigation-Search"></a>Search</h3>
+<p>
+</p><form enctype="application/x-www-form-urlencoded" method="get"
id="cse-search-box" action="http://www.google.com/cse";>
+ <div>
+ <input type="hidden" name="cx" value="002890367768291051730:o99qiwa09y4">
+ <input type="hidden" name="ie" value="UTF-8">
+ <input type="text" name="q" size="21">
+ <input type="submit" name="sa" value="Search">
+ </div>
+</form>
+<script type="text/javascript"
src="http://www.google.com/cse/brand?form=cse-search-box&lang=en";></script>
+
+
+<h3><a shape="rect" name="Navigation-Developers"></a>Developers</h3>
+
+<ul class="alternate" type="square"><li><a shape="rect"
href="http://cxf.apache.org/docs/cxf-architecture.html";>Architecture
Guide</a></li><li><a shape="rect" href="source-repository.html" title="Source
Repository">Source Repository</a></li><li><a shape="rect" href="building.html"
title="Building">Building</a></li><li><a shape="rect"
href="automated-builds.html" title="Automated Builds">Automated
Builds</a></li><li><a shape="rect" href="testing-debugging.html"
title="Testing-Debugging">Testing-Debugging</a></li><li><a shape="rect"
href="coding-guidelines.html" title="Coding Guidelines">Coding
Guidelines</a></li><li><a shape="rect" href="getting-involved.html"
title="Getting Involved">Getting Involved</a></li><li><a shape="rect"
href="release-management.html" title="Release Management">Release
Management</a></li></ul>
+
+
+<h3><a shape="rect" name="Navigation-Subprojects"></a>Subprojects</h3>
+
+<ul class="alternate" type="square"><li><a shape="rect"
href="distributed-osgi.html" title="Distributed OSGi">Distributed
OSGi</a></li><li><a shape="rect" href="xjc-utils.html" title="XJC Utils">XJC
Utils</a></li><li><a shape="rect" href="build-utils.html" title="Build
Utils">Build Utils</a></li><li><a shape="rect" href="fediz.html"
title="Fediz">Fediz</a></li></ul>
+
+
+<h3><a shape="rect" name="Navigation-ASF"></a><a shape="rect"
class="external-link" href="http://www.apache.org";>ASF</a></h3>
+
+<ul class="alternate" type="square"><li><a shape="rect" class="external-link"
href="http://www.apache.org/foundation/how-it-works.html";>How Apache
Works</a></li><li><a shape="rect" class="external-link"
href="http://www.apache.org/foundation/";>Foundation</a></li><li><a shape="rect"
class="external-link"
href="http://www.apache.org/foundation/sponsorship.html";>Sponsor
Apache</a></li><li><a shape="rect" class="external-link"
href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li><li><a
shape="rect" class="external-link"
href="http://www.apache.org/security/";>Security</a></li></ul>
+</div>
+ <!-- NavigationBar -->
+ </div>
+ </div>
+ </div>
+ </div>
+ </td>
+ <td height="100%">
+ <!-- Content -->
+ <div class="wiki-content">
+<div id="ConfluenceContent"><h1><a shape="rect"
name="FedizIDP1.1-FedizIDP"></a>Fediz IDP</h1>
+
+<p>The Release 1.1 introduces the following new feature:</p>
+
+<ul><li>Federation Metadata<br clear="none">
+The IDP supports publishing the WS-Federation Metadata document which allows
to more easily integrate the IDP into platforms which support referencing a
Metadata document. Metadata consists of the signing certificate, the provided
claims, etc.</li></ul>
+
+
+<ul><li>Spring Web Flow support<br clear="none">
+The IDP has been refactored to use Spring Web Flow to manage the federation
flow. This provides flexibility to be able to customize the IDP to company's
specific requirements. The IDP is secured by Spring Security to get the
benefits and flexibility of Spring Security.</li></ul>
+
+
+<ul><li>Resource IDP and Home Realm Discovery<br clear="none">
+This is the major new feature. The IDP is able to figure out from which
security domain/realm the browser request is coming from to redirect the
sign-in request to the requestor IDP which does the authentication and issues a
token which is sent to the Resource IDP. The Resource IDP will then either map
the principal from one security domain to the target security domain and get
claims information of the mapped principal or transform the claims information
and finally issue a new token for the relying party (application).</li></ul>
+
+
+
+<p>The Fediz Identity Provider (IDP) consists of two WAR files. One is the
Security Token Service (STS) component, fediz-idp-sts.war, which is responsible
for validating credentials, getting the requested claims data and issuing a
SAML token. There is no easy way for Web browsers to issue SOAP requests to the
STS directly, necessitating the second component, an IDP WAR (fediz-idp.war)
which allows browser-based applications to interact with the STS. The
communication between the browser and the IDP must be performed within the
confines of the base HTTP 1.1 functionality and conform as closely as possible
to the WS-Trust protocols semantic.</p>
+
+<p>The Fediz STS is based on a customized CXF STS configured to support
standard Federation use cases demonstrated by the examples. The Fediz STS has
been enhanced to support two realms *Realm-A* and *Realm-B* with the following
set of users:</p>
+<div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> User </th><th colspan="1" rowspan="1"
class="confluenceTh"> Password<br clear="none" class="atl-forced-newline">
</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <em>Realm
A</em><br clear="none" class="atl-forced-newline"> </td><td colspan="1"
rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> alice<br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> ecila<br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> bob<br
clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> bob<br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> ted<br
clear="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> det<br
clear="none" class="atl-forced-newline"> </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <em>Realm B</em><br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> ALICE<br clear="none" class="atl-forced-newline">
</td><td colspan="1" rowspan="1" class="confluenceTd"> ECILA<br clear="none"
class="atl-forced-newline"> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> BOB<br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> BOB<br clear="none"
class="atl-forced-newline"> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> TED<br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> DET<br clear="none"
class="atl-forced-newline"> </td></tr></tbody></table>
+</div>
+
+
+<p>The Fediz IDP doesn't support several realms within one WAR which requires
to build a Fediz IDP WAR for Realm A (default, shipped with Fediz Distribution)
and Realm B. See below how to build a Fediz IDP WAR for a specific realm.</p>
+
+<h3><a shape="rect" name="FedizIDP1.1-Installation"></a>Installation</h3>
+
+<p>The Fediz IDP has been tested with Tomcat 6 and 7 but should be able to
work with any commercial JEE application server.</p>
+
+<p>It's recommended to set up a dedicated (separate) Tomcat instance for the
IDP compared to the one hosting the RP (relying party) applications. Using
one deployment of Tomcat with multiple CATALINA_BASE instances, as described <a
shape="rect" class="external-link"
href="http://www.shaunabram.com/multiple-tomcat-instances/";
rel="nofollow">here</a> is one option but note any libs in $CATALINA_HOME/lib
folder will be shared throughout each of the activated CATALINA_BASE instances.
Another probably simpler alternative is to copy your Tomcat folder into a
second location and edit its conf/server.xml file and <a shape="rect"
class="external-link"
href="http://viralpatel.net/blogs/2009/08/running-multiple-instance-apache-tomcat-single-server.html";
rel="nofollow">change port values</a> (discussed below) so they don't conflict
with the original Tomcat installation.</p>
+
+<p>To start and stop this second Tomcat instance, it is perhaps easiest to
create small startup.sh and shutdown.sh scripts that temporarily redefine
$CATALINA_HOME from the first to the second instance, for example:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+CATALINA_HOME=/path/to/second/tomcat
+$CATALINA_HOME/bin/startup.sh
+]]></script>
+</div></div>
+
+<p>and</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+CATALINA_HOME=/path/to/second/tomcat
+$CATALINA_HOME/bin/shutdown.sh
+]]></script>
+</div></div>
+
+<p>If you're using the one Tomcat with multiple instance option, it's
$CATALINA_BASE instead that will need to be redefined above.</p>
+
+<h5><a shape="rect"
name="FedizIDP1.1-Tomcatserver.xmlconfiguration"></a>Tomcat server.xml
configuration</h5>
+
+<p>The Fediz examples use the following Tomcat port values for the IDP/STS,
defined in the conf/server.xml file. We use ports different from the Tomcat
defaults so as not to conflict with the Tomcat instance running the RP
applications.</p>
+
+<ul><li>HTTP port: 9080 (used for Maven deployment, mvn
tomcat:redeploy)</li><li>HTTPS port: 9443 (where IDP and STS are
accessed)</li><li>Server port: 9005 (for shutdown and other commands)</li></ul>
+
+
+<p>Here is a sample snippet for showing the configuration of the above three
values:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<Server port="9005" shutdown="SHUTDOWN">
+...
+
+ <!-- http configuration -->
+ <Connector port="9080" protocol="HTTP/1.1"
+ connectionTimeout="20000"
+ redirectPort="9443" />
+
+ ...
+
+ <!-- https configuration -->
+ <Connector port="9443" protocol="HTTP/1.1" SSLEnabled="true"
+ maxThreads="150" scheme="https" secure="true"
+ keystoreFile="idp-ssl-server.jks"
+ keystorePass="tompass" sslProtocol="TLS" />
+ ...
+
+ <Connector port="9009" protocol="AJP/1.3" redirectPort="9443" />
+
+...
+</Server>
+]]></script>
+</div></div>
+
+<p>The keystoreFile is relative to $CATALINA_BASE. See <a shape="rect"
class="external-link"
href="http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html";>here</a> for the
Tomcat 7 configuration reference. This page also describes how to create
certificates. Sample Tomcat keystores (not for production use, but useful for
demoing Fediz and running the sample applications) are provided in the
examples/samplekeys folder of the Fediz distribution.</p>
+
+<p>To establish trust, there are significant keystore/truststore requirements
between the Tomcat instances and the various web applications (IDP, STS,
Relying party applications, third party web services, etc.) See <a
shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/cxf/fediz/tags/fediz-1.1.0/examples/samplekeys/HowToGenerateKeysREADME.html?revision=1538770&view=co";>this
page</a> for more details, it lists the trust requirements as well as sample
scripts for creating your own (self-signed) keys.</p>
+
+<p><b>Warning: All sample keystores provided with Fediz (including in the WAR
files for its services and examples) are for development/prototyping use only.
They'll need to be replaced for production use, at a minimum with your own
self-signed keys but strongly recommended to use third-party signed
keys.</b></p>
+
+<h5><a shape="rect" name="FedizIDP1.1-BuildtheIDPWAR"></a>Build the IDP
WAR</h5>
+
+<p>The Fediz 1.1 distribution ships one Fediz IDP WAR built for Realm-A by
default. The distribution also contains the IDP and STS sources with two Maven
Profiles <em>realm-a</em> and <em>realm-b</em>. More information is provided in
the {{README.txt} <a shape="rect" class="external-link"
href="http://svn.apache.org/viewvc/cxf/fediz/tags/fediz-1.1.0/services/idp/README.txt?view=co";>here</a></p>
+
+<p>Once you deploy the IDP WAR files to your Tomcat installation
(<catalina.home>/webapps), you should be able to see the Fediz STS from a
browser at <a shape="rect" class="external-link"
href="http://localhost:9080/fediz-idp-sts/STSService?wsdl";
rel="nofollow">http://localhost:9080/fediz-idp-sts/STSService?wsdl</a> ,
assuming you're using port 9080 as listed above.</p>
+
+
+<h3><a shape="rect" name="FedizIDP1.1-Configuration"></a>Configuration</h3>
+
+<p>You can manage the users, their claims and the claims per application in
the IDP.</p>
+
+<h5><a shape="rect" name="FedizIDP1.1-Userandpassword"></a>User and
password</h5>
+
+<p>The users and passwords are configured in a Spring configuration file in
<tt>webapps/fediz-idp-sts/WEB-INF/passwords.xml</tt>. The following users are
already configured for the <em>Realm A</em> and can easily be extended.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
+ <util:map id="passwords">
+ <entry key="alice"
+ value="ecila" />
+ <entry key="bob"
+ value="bob" />
+ <entry key="ted"
+ value="det" />
+ </util:map>
+]]></script>
+</div></div>
+
+<h5><a shape="rect" name="FedizIDP1.1-UserClaims"></a>User Claims</h5>
+
+<p>The claims of each user are configured in a spring configuration file
<tt>webapps/fediz-idp-sts/WEB-INF/userClaims.xml</tt>. The following claims are
already configured:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
+ <util:map id="userClaimsREALMA">
+ <entry key="alice"
+ value-ref="REALMA_aliceClaims" />
+ <entry key="bob"
+ value-ref="REALMA_bobClaims" />
+ <entry key="ted"
+ value-ref="REALMA_tedClaims" />
+ </util:map>
+
+ <util:map id="REALMA_aliceClaims">
+ <entry
key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname";
+ value="Alice" />
+ <entry
key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname";
+ value="Smith" />
+ <entry
key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress";
+ value="[email protected]" />
+ <entry key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/role";
+ value="User" />
+ </util:map>
+]]></script>
+</div></div>
+
+<p>The claim id's are configured according to Section 7.5 in the specification
<a shape="rect" class="external-link"
href="http://docs.oasis-open.org/imi/identity/v1.0/identity.html";
rel="nofollow">Identity Metasystem Interoperability</a>. The mapping of claims
to a SAML attribute statement are described in Section 7.2.</p>
+
+<h5><a shape="rect" name="FedizIDP1.1-Applicationclaims"></a>Application
claims</h5>
+
+<p><em>Note: The configuration file</em> <tt><em>RPClaims.xml</em></tt>
<em>has been replaced</em></p>
+
+<p>The required claims per relying party are configured in the new IDP
configuration file <tt>idp-config-<realm>.xml</tt> which has been
enhanced to support other configuration parameters as well:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
+ <bean id="srv-fedizhelloworld"
class="org.apache.cxf.fediz.service.idp.model.ServiceConfig">
+ <property name="realm"
value="urn:org:apache:cxf:fediz:fedizhelloworld" />
+ <property name="protocol"
value="http://docs.oasis-open.org/wsfed/federation/200706"; />
+ <property name="serviceDisplayName" value="Fedizhelloworld" />
+ <property name="serviceDescription" value="Web Application to
illustrate WS-Federation" />
+ <property name="role" value="ApplicationServiceType" />
+ <property name="tokenType"
value="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0";
/>
+ <property name="lifeTime" value="3600" />
+ <property name="requestedClaims">
+ <util:list>
+ <bean
class="org.apache.cxf.fediz.service.idp.model.RequestClaim">
+ <property name="claimType"
value="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname"; />
+ <property name="optional" value="false" />
+ </bean>
+ <bean
class="org.apache.cxf.fediz.service.idp.model.RequestClaim">
+ <property name="claimType"
value="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"; />
+ <property name="optional" value="false" />
+ </bean>
+ <bean
class="org.apache.cxf.fediz.service.idp.model.RequestClaim">
+ <property name="claimType"
value="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"; />
+ <property name="optional" value="false" />
+ </bean>
+ <bean
class="org.apache.cxf.fediz.service.idp.model.RequestClaim">
+ <property name="claimType"
value="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/role"; />
+ <property name="optional" value="true" />
+ </bean>
+ </util:list>
+ </property>
+ </bean>
+]]></script>
+</div></div>
+
+
+<h3><a shape="rect" name="FedizIDP1.1-ConfigureLDAPdirectory"></a>Configure
LDAP directory</h3>
+
+<p>The Fediz IDP can be configured to attach an LDAP directory to authenticate
users and to retrieve claims information of users.</p>
+
+<h5><a shape="rect"
name="FedizIDP1.1-Usernameandpasswordauthentication"></a>Username and password
authentication</h5>
+
+<p>WSS4J supports username/password authentication using JAAS. The JDK
provides a JAAS LoginModule for LDAP which can be configured as illustrated
here in a sample jaas configuration (jaas.config):</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+myldap {
+ com.sun.security.auth.module.LdapLoginModule REQUIRED
+ userProvider=ldap://ldap.mycompany.org:389/OU=Users,DC=mycompany,DC=org";
+ authIdentity="cn={USERNAME},OU=Users,DC=mycompany,DC=org"
+ useSSL=false
+ debug=true;
+};
+]]></script>
+</div></div>
+
+<p>You can get more information about this LoginModule <a shape="rect"
class="external-link"
href="http://download.oracle.com/javase/6/docs/jre/api/security/jaas/spec/com/sun/security/auth/module/LdapLoginModule.html";
rel="nofollow">here</a>.</p>
+
+<p>In this example, all the users are stored in the organization unit Users
within mycompany.org. The configuration filename can be chosen, e.g.
<tt>jaas.config</tt>. The filename must be configured as a JVM argument. JVM
related configurations for Tomcat can be done in the file
<tt>setenv.sh/bat</tt> located in directory <tt>tomcat/bin</tt>. This script is
called implicitly by <tt>catalina.bat/sh</tt> and might look like this for
UNIX:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
+#!/bin/sh
+JAVA_OPTS="-Djava.security.auth.login.config=/opt/tomcat/conf/jaas.config"
+export JAVA_OPTS
+]]></script>
+</div></div>
+
+<p>Next, the STS endpoint has to be configured to use the JAAS LoginModule
which is accomplished by the <tt>JAASUsernameTokenValidator</tt>.</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<bean
+ class="org.apache.ws.security.validate.JAASUsernameTokenValidator"
+ id="jaasUTValidator">
+ <property name="contextName" value="myldap"/>
+</bean>
+
+<jaxws:endpoint id="transportSTSUT"
+ endpointName="ns1:TransportUT_Port"
+ serviceName="ns1:SecurityTokenService"
+ xmlns:ns1=http://docs.oasis-open.org/ws-sx/ws-trust/200512/
+ wsdlLocation="/WEB-INF/wsdl/ws-trust-1.4-service.wsdl"
+ address="/STSServiceTransportUT"
+ implementor="#transportSTSProviderBean">
+
+ <jaxws:properties>
+ <entry key="ws-security.ut.validator"
+ value-ref="jaasUTValidator"/>
+ </jaxws:properties>
+</jaxws:endpoint>
+]]></script>
+</div></div>
+
+<p>The property <tt>contextName</tt> must match the context name defined in
the JAAS configuration file which is <tt>myldap</tt> in this example.</p>
+
+<h5><a shape="rect" name="FedizIDP1.1-Claimsmanagement"></a>Claims
management</h5>
+
+<p>When a STS client (IDP) requests a claim, the ClaimsManager in the STS
checks every registered ClaimsHandler who can provide the data of the requested
claim. The CXF STS provides
<tt>org.apache.cxf.sts.claims.LdapClaimsHandler</tt> which is a claims handler
implementation to get claims from user attributes in a LDAP directory.</p>
+
+<p>You configure which claim URI maps to which LDAP user attribute. The
implementation uses the Spring Ldap Module (LdapTemplate).</p>
+
+<p>The following example illustrate the changes to be made in
<tt>webapps/fediz-idp-sts/WEB-INF/cxf-transport.xml</tt>:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
+<util:list id="claimHandlerList">
+ <ref bean="ldapClaimsHandler" />
+</util:list>
+
+<bean id="contextSource"
+ class="org.springframework.ldap.core.support.LdapContextSource">
+ <property name="url" value="ldap://ldap.mycompany.org:389"; />
+ <property name="userDn"
+ value="CN=techUser,OU=Users,DC=mycompany,DC=org" />
+ <property name="password" value="mypassword" />
+</bean>
+
+<bean id="ldapTemplate"
+ class="org.springframework.ldap.core.LdapTemplate">
+ <constructor-arg ref="contextSource" />
+</bean>
+
+<util:map id="claimsToLdapAttributeMapping">
+ <entry
+key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname";
+value="givenName" />
+ <entry key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname";
+value="sn" />
+ <entry
+key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress";
+value="mail" />
+ <entry key="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/country";
+value="c" />
+</util:map>
+
+<bean id="ldapClaimsHandler"
+ class="org.apache.cxf.sts.claims.LdapClaimsHandler">
+ <property name="ldapTemplate" ref="ldapTemplate" />
+ <property name="claimsLdapAttributeMapping"
+ ref="claimsToLdapAttributeMapping" />
+ <property name="userBaseDN"
+ value="OU=Users,DC=mycompany,DC=org" />
+</bean>
+]]></script>
+</div></div>
+
+<p>You must deploy the library for the spring ldap module and its
dependencies. The POM of the spring ldap module is available <a shape="rect"
class="external-link"
href="http://repo1.maven.org/maven2/org/springframework/ldap/spring-ldap/1.2/spring-ldap-1.2.pom";
rel="nofollow">here</a>.</p>
+
+<p>You can add the dependency to spring ldap module to the Fediz STS POM, add
the above configuration and rebuild the STS component or do the configuration
in the deployed STS directly and add the following JAR files:</p>
+
+<ul><li>lang-2.1.0.jar</li><li>ldapbp-1.0.jar</li><li>spring-ldap-1.2.jar</li></ul>
+</div>
+ </div>
+ <!-- Content -->
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td id="cell-2-2" colspan="2"> </td>
+ </tr>
+ <tr>
+ <td id="cell-3-0"> </td>
+ <td id="cell-3-1"> </td>
+ <td id="cell-3-2">
+ <div id="footer">
+ <!-- Footer -->
+ <div id="site-footer">
+ <a href="http://cxf.apache.org/privacy-policy.html";>Privacy
Policy</a> -
+ (<a
href="https://cwiki.apache.org/confluence/pages/editpage.action?pageId=34838916";>edit
page</a>)
+ (<a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34838916&showComments=true&showCommentArea=true#addcomment";>add
comment</a>)<br>
+ Apache CXF, CXF, Apache, the Apache feather logo are trademarks of The
Apache Software Foundation.<br>
+ All other marks mentioned may be trademarks or registered trademarks
of their respective owners.
+ </div>
+ <!-- Footer -->
+ </div>
+ </td>
+ <td id="cell-3-3"> </td>
+ <td id="cell-3-4"> </td>
+ </tr>
+ <tr>
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1"> </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+</table>
+
+<script type="text/javascript">
+var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl."; :
"http://www.";);
+document.write(unescape("%3Cscript src='" + gaJsHost +
"google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
+</script>
+<script type="text/javascript">
+try {
+var pageTracker = _gat._getTracker("UA-4458903-1");
+pageTracker._trackPageview();
+} catch(err) {}</script>
+
+</body>
+</html>
+
![http://cxf.apache.org/images/asf-logo.png"](http://cxf.apache.org/images/asf-logo.png"){kind=link}