cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache CXF > Fediz IDP
Date Tue, 15 Jan 2013 16:08:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/15/_/styles/combined.css?spaceKey=CXF&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/CXF/Fediz+IDP">Fediz
IDP</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~coheigea@apache.org">Colm
O hEigeartaigh</a>
    </h4>
        <br/>
                         <h4>Changes (2)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-unchanged" >h1. Fediz IDP <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >The Fediz Identity Provider (IDP)
consists of two WAR files. One is the Security Token Service (STS) component, <span class="diff-changed-words">fediz<span
class="diff-added-chars"style="background-color: #dfd;">-</span>idp<span class="diff-added-chars"style="background-color:
#dfd;">-</span>sts.war,</span> 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
<span class="diff-changed-words">(fediz<span class="diff-added-chars"style="background-color:
#dfd;">-</span>idp.war)</span> 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. <br></td>!
 </tr>
            <tr><td class="diff-unchanged" > <br>The Fediz STS is based
on a customized CXF STS configured to support standard Federation use cases demonstrated by
the examples. <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >*Warning:  All sample keystores provided
with Fediz (including in the WAR files for its services and examples) are for development/prototyping
use only.  They&#39;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.* <br>
<br></td></tr>
            <tr><td class="diff-changed-lines" >Once you deploy the IDP WAR files
to your Tomcat installation (&lt;catalina.home&gt;/webapps), you should be able to
see the Fediz STS from a browser at <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">http://localhost:9080/fedizidpsts/STSService?wsdl,</span>
<span class="diff-added-words"style="background-color: #dfd;">http://localhost:9080/fediz-idp-sts/STSService?wsdl
(note that prior to 1.0.3 the war name is actually &quot;fedizidpsts&quot;),</span>
assuming you&#39;re using port 9080 as listed above. <br></td></tr>
            <tr><td class="diff-unchanged" > <br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h1><a name="FedizIDP-FedizIDP"></a>Fediz IDP</h1>

<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.</p>

<h3><a name="FedizIDP-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 href="http://www.shaunabram.com/multiple-tomcat-instances/"
class="external-link" 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 href="http://viralpatel.net/blogs/2009/08/running-multiple-instance-apache-tomcat-single-server.html"
class="external-link" 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">
<pre class="code-java">
CATALINA_HOME=/path/to/second/tomcat
$CATALINA_HOME/bin/startup.sh
</pre>
</div></div>

<p>and</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
CATALINA_HOME=/path/to/second/tomcat
$CATALINA_HOME/bin/shutdown.sh
</pre>
</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 name="FedizIDP-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 (for shutdown and other commands): 9005</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">
<pre class="code-xml">
<span class="code-tag">&lt;Server port=<span class="code-quote">"9005"</span>
shutdown=<span class="code-quote">"SHUTDOWN"</span>&gt;</span>
...

   <span class="code-tag"><span class="code-comment">&lt;!-- http configuration
--&gt;</span></span>
   &lt;Connector port=<span class="code-quote">"9080"</span> protocol=<span
class="code-quote">"HTTP/1.1"</span>
        connectionTimeout=<span class="code-quote">"20000"</span>
        redirectPort=<span class="code-quote">"9443"</span> /&gt;

   ...

   <span class="code-tag"><span class="code-comment">&lt;!-- https configuration
--&gt;</span></span>
   &lt;Connector port=<span class="code-quote">"9443"</span> protocol=<span
class="code-quote">"HTTP/1.1"</span> SSLEnabled=<span class="code-quote">"true"</span>
        maxThreads=<span class="code-quote">"150"</span> scheme=<span class="code-quote">"https"</span>
secure=<span class="code-quote">"true"</span>
        keystoreFile=<span class="code-quote">"tomcat-idp.jks"</span>
        keystorePass=<span class="code-quote">"tompass"</span> sslProtocol=<span
class="code-quote">"TLS"</span> /&gt;
   ...
 
   <span class="code-tag">&lt;Connector port=<span class="code-quote">"9009"</span>
protocol=<span class="code-quote">"AJP/1.3"</span> redirectPort=<span class="code-quote">"9443"</span>
/&gt;</span>

...
<span class="code-tag">&lt;/Server&gt;</span>
</pre>
</div></div>

<p>The keystoreFile is relative to $CATALINA_HOME. See <a href="http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html"
class="external-link" rel="nofollow">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 href="http://svn.apache.org/viewvc/cxf/fediz/trunk/examples/samplekeys/HowToGenerateKeysREADME.html?view=co"
class="external-link" rel="nofollow">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>

<p>Once you deploy the IDP WAR files to your Tomcat installation (&lt;catalina.home&gt;/webapps),
you should be able to see the Fediz STS from a browser at <a href="http://localhost:9080/fediz-idp-sts/STSService?wsdl"
class="external-link" rel="nofollow">http://localhost:9080/fediz-idp-sts/STSService?wsdl</a>
(note that prior to 1.0.3 the war name is actually "fedizidpsts"), assuming you're using port
9080 as listed above.</p>


<h3><a name="FedizIDP-Configuration"></a>Configuration</h3>

<p>You can manage the users, their claims and the claims per application in the IDP.</p>

<h5><a name="FedizIDP-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 and can easily be extended.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
    <span class="code-tag">&lt;util:map id=<span class="code-quote">"passwords"</span>&gt;</span>
        &lt;entry key=<span class="code-quote">"alice"</span>
            value=<span class="code-quote">"ecila"</span> /&gt;
        &lt;entry key=<span class="code-quote">"bob"</span>
            value=<span class="code-quote">"bob"</span> /&gt;
        &lt;entry key=<span class="code-quote">"ted"</span>
            value=<span class="code-quote">"det"</span> /&gt;
    <span class="code-tag">&lt;/util:map&gt;</span>
</pre>
</div></div>

<h5><a name="FedizIDP-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">
<pre class="code-xml">
    <span class="code-tag">&lt;util:map id=<span class="code-quote">"userClaims"</span>&gt;</span>
        &lt;entry key=<span class="code-quote">"alice"</span>
            value-ref=<span class="code-quote">"aliceClaims"</span> /&gt;
        &lt;entry key=<span class="code-quote">"bob"</span>
            value-ref=<span class="code-quote">"bobClaims"</span> /&gt;
        &lt;entry key=<span class="code-quote">"ted"</span>
            value-ref=<span class="code-quote">"tedClaims"</span> /&gt;
    <span class="code-tag">&lt;/util:map&gt;</span>
   
    <span class="code-tag">&lt;util:map id=<span class="code-quote">"aliceClaims"</span>&gt;</span>
        &lt;entry key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname"</span>
            value=<span class="code-quote">"Alice"</span> /&gt;
        &lt;entry key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"</span>
            value=<span class="code-quote">"Smith"</span> /&gt;
        &lt;entry key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"</span>
            value=<span class="code-quote">"alice@mycompany.org"</span> /&gt;
        &lt;entry key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/role"</span>
            value=<span class="code-quote">"user"</span> /&gt;
           
    <span class="code-tag">&lt;/util:map&gt;</span>
</pre>
</div></div>

<p>The claim id's are configured according to Section 7.5 in the specification <a
href="http://docs.oasis-open.org/imi/identity/v1.0/identity.html" class="external-link" rel="nofollow">Identity
Metasystem Interoperability</a>. The mapping of claims to a SAML attribute statement
are described in Section 7.2.</p>

<h5><a name="FedizIDP-Applicationclaims"></a>Application claims</h5>

<p>The required claims per relying party are configured in the <tt>webapps/fediz-idp/WEB-INF/RPClaims.xml</tt>.
The XML file has the following structure:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
    <span class="code-tag">&lt;util:map id=<span class="code-quote">"realm2ClaimsMap"</span>&gt;</span>
        &lt;entry key=<span class="code-quote">"https://localhost:8443/fedizhelloworld/"</span>
            value-ref=<span class="code-quote">"claimsWsfedhelloworld"</span>
/&gt;
    <span class="code-tag">&lt;/util:map&gt;</span>

    <span class="code-tag">&lt;util:list id=<span class="code-quote">"claimsWsfedhelloworld"</span>&gt;</span>
        <span class="code-tag">&lt;value&gt;</span>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname<span
class="code-tag">&lt;/value&gt;</span>
        <span class="code-tag">&lt;value&gt;</span>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname<span
class="code-tag">&lt;/value&gt;</span>
        <span class="code-tag">&lt;value&gt;</span>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress<span
class="code-tag">&lt;/value&gt;</span>
        <span class="code-tag">&lt;value&gt;</span>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/role<span
class="code-tag">&lt;/value&gt;</span>
    <span class="code-tag">&lt;/util:list&gt;</span>   
</pre>
</div></div>

<p>The key of each map entry must match with the <tt>wtrealm</tt> paramater
in the redirect triggered by the relying party. The required claims for the different type
of applications are grouped in beans which are a list of Strings as illustrated in <tt>claimsWsfedhelloworld</tt>.</p>

<p>The bean <tt>realm2ClaimsMap</tt> must be named realm2ClaimsMap and maps
the different Relying Parties (applications) to one of the claim lists. This map is required
to manage which claims are required for the applications.</p>

<p>The JIRA issue <a href="https://issues.apache.org/jira/browse/FEDIZ-1" class="external-link"
rel="nofollow">FEDIZ-1</a> will provide another option to manage the required claims
on the Relying Party side.</p>

<h3><a name="FedizIDP-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 name="FedizIDP-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">
<pre class="code-java">
myldap {
 com.sun.security.auth.module.LdapLoginModule REQUIRED
 userProvider=ldap:<span class="code-comment">//ldap.mycompany.org:389/OU=Users,DC=mycompany,DC=org"
</span> authIdentity=<span class="code-quote">"cn={USERNAME},OU=Users,DC=mycompany,DC=org"</span>
 useSSL=<span class="code-keyword">false</span>
 debug=<span class="code-keyword">true</span>;
};
</pre>
</div></div>

<p>You can get more information about this LoginModule <a href="http://download.oracle.com/javase/6/docs/jre/api/security/jaas/spec/com/sun/security/auth/module/LdapLoginModule.html"
class="external-link" 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">
<pre class="code-java">
#!/bin/sh
JAVA_OPTS=<span class="code-quote">"-Djava.security.auth.login.config=/opt/tomcat/conf/jaas.config"</span>
export JAVA_OPTS
</pre>
</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">
<pre class="code-xml">
&lt;bean
  class=<span class="code-quote">"org.apache.ws.security.validate.JAASUsernameTokenValidator"</span>
      id=<span class="code-quote">"jaasUTValidator"</span>&gt;
   <span class="code-tag">&lt;property name=<span class="code-quote">"contextName"</span>
value=<span class="code-quote">"myldap"</span>/&gt;</span>
<span class="code-tag">&lt;/bean&gt;</span>

&lt;jaxws:endpoint id=<span class="code-quote">"transportSTSUT"</span>
  endpointName=<span class="code-quote">"ns1:TransportUT_Port"</span>
  serviceName=<span class="code-quote">"ns1:SecurityTokenService"</span>
  <span class="code-keyword">xmlns:ns1</span>=http://docs.oasis-open.org/ws-sx/ws-trust/200512/
  wsdlLocation=<span class="code-quote">"/WEB-INF/wsdl/ws-trust-1.4-service.wsdl"</span>
  address=<span class="code-quote">"/STSServiceTransportUT"</span>
  implementor=<span class="code-quote">"#transportSTSProviderBean"</span>&gt;

  <span class="code-tag">&lt;jaxws:properties&gt;</span>
    &lt;entry key=<span class="code-quote">"ws-security.ut.validator"</span>
         value-ref=<span class="code-quote">"jaasUTValidator"</span>/&gt;
  <span class="code-tag">&lt;/jaxws:properties&gt;</span>
<span class="code-tag">&lt;/jaxws:endpoint&gt;</span>
</pre>
</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 name="FedizIDP-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">
<pre class="code-xml">
<span class="code-tag">&lt;util:list id=<span class="code-quote">"claimHandlerList"</span>&gt;</span>
  <span class="code-tag">&lt;ref bean=<span class="code-quote">"ldapClaimsHandler"</span>
/&gt;</span>
<span class="code-tag">&lt;/util:list&gt;</span>

&lt;bean id=<span class="code-quote">"contextSource"</span>
   class=<span class="code-quote">"org.springframework.ldap.core.support.LdapContextSource"</span>&gt;
  <span class="code-tag">&lt;property name=<span class="code-quote">"url"</span>
value=<span class="code-quote">"ldap://ldap.mycompany.org:389"</span> /&gt;</span>
  &lt;property name=<span class="code-quote">"userDn"</span>
    value=<span class="code-quote">"CN=techUser,OU=Users,DC=mycompany,DC=org"</span>
/&gt;
  <span class="code-tag">&lt;property name=<span class="code-quote">"password"</span>
value=<span class="code-quote">"mypassword"</span> /&gt;</span>
<span class="code-tag">&lt;/bean&gt;</span>

&lt;bean id=<span class="code-quote">"ldapTemplate"</span>
   class=<span class="code-quote">"org.springframework.ldap.core.LdapTemplate"</span>&gt;
  <span class="code-tag">&lt;constructor-arg ref=<span class="code-quote">"contextSource"</span>
/&gt;</span>
<span class="code-tag">&lt;/bean&gt;</span>

<span class="code-tag">&lt;util:map id=<span class="code-quote">"claimsToLdapAttributeMapping"</span>&gt;</span>
  &lt;entry
key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname"</span>
value=<span class="code-quote">"givenName"</span> /&gt;
  &lt;entry key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"</span>
value=<span class="code-quote">"sn"</span> /&gt;
  &lt;entry
key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"</span>
value=<span class="code-quote">"mail"</span> /&gt;
  &lt;entry key=<span class="code-quote">"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/country"</span>
value=<span class="code-quote">"c"</span> /&gt;
<span class="code-tag">&lt;/util:map&gt;</span>

&lt;bean id=<span class="code-quote">"ldapClaimsHandler"</span>
    class=<span class="code-quote">"org.apache.cxf.sts.claims.LdapClaimsHandler"</span>&gt;
  <span class="code-tag">&lt;property name=<span class="code-quote">"ldapTemplate"</span>
ref=<span class="code-quote">"ldapTemplate"</span> /&gt;</span>
  &lt;property name=<span class="code-quote">"claimsLdapAttributeMapping"</span>
            ref=<span class="code-quote">"claimsToLdapAttributeMapping"</span>
/&gt;
  &lt;property name=<span class="code-quote">"userBaseDN"</span>
      value=<span class="code-quote">"OU=Users,DC=mycompany,DC=org"</span> /&gt;
<span class="code-tag">&lt;/bean&gt;</span>
</pre>
</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 href="http://repo1.maven.org/maven2/org/springframework/ldap/spring-ldap/1.2/spring-ldap-1.2.pom"
class="external-link" 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 id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/CXF/Fediz+IDP">View Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=27846949&revisedVersion=18&originalVersion=17">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/CXF/Fediz+IDP?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message