You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by bu...@apache.org on 2015/07/06 00:34:38 UTC
svn commit: r957126 [15/18] - in /websites/staging/directory/trunk/content:
./ apacheds/ apacheds/advanced-ug/ apacheds/basic-ug/
apacheds/configuration/ apacheds/kerberos-ug/ api/ api/download/
api/groovy-api/ api/user-guide/ escimo/ fortress/ fortres...
Modified: websites/staging/directory/trunk/content/fortress/overview.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/overview.html (original)
+++ websites/staging/directory/trunk/content/fortress/overview.html Sun Jul 5 22:34:35 2015
@@ -160,11 +160,22 @@
-<h1 id="fortress-overview">Fortress Overview</h1>
-<h2 id="rationale">Rationale</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fortress-overview">Fortress Overview<a class="headerlink" href="#fortress-overview" title="Permanent link">¶</a></h1>
+<h2 id="rationale">Rationale<a class="headerlink" href="#rationale" title="Permanent link">¶</a></h2>
<p>FORTRESS was built to the highest standards of security combined with easy installation and ongoing maintenance. It allows service providers to avoid vendor lock-in, high licensing costs and steep learning curves.</p>
<p>This security system was designed to be deployed into a wide variety of system environments easily. Adopters need not have expertise in Unix, LDAP or other system technologies to install, maintain and use. The result is a high-quality, low-cost solution for identity and access control.</p>
-<h2 id="what-is-it">What is it?</h2>
+<h2 id="what-is-it">What is it?<a class="headerlink" href="#what-is-it" title="Permanent link">¶</a></h2>
<p>Fortress is a standards-based and open source IAM system that provides ANSI RBAC (INCITS 359) management and enforcement capabilities to networked applications and systems. </p>
<p>Included in Fortress packages:</p>
<ul>
@@ -175,7 +186,7 @@
<li>Directory Services with <a href="http://www.openldap.org">OpenLDAP</a> (powered w/Memory-Mapped DB) or <a href="http://directory.apache.org">ApacheDS</a></li>
</ul>
<p>It is released under terms of the Apache License 2.0. </p>
-<h2 id="what-can-it-do-currently">What can it do currently?</h2>
+<h2 id="what-can-it-do-currently">What can it do currently?<a class="headerlink" href="#what-can-it-do-currently" title="Permanent link">¶</a></h2>
<p>A demo outlining this capability using embedded Apache Tomcat Server and Realm RBAC Policy Enforcement contained within QUICKSTART packages. </p>
<p>Features include...</p>
<ul>
@@ -192,27 +203,27 @@
<li>Javadoc API guide </li>
<li>Customizable Samples to show common API usages</li>
</ul>
-<h2 id="what-technologies-at-play">What technologies at play?</h2>
+<h2 id="what-technologies-at-play">What technologies at play?<a class="headerlink" href="#what-technologies-at-play" title="Permanent link">¶</a></h2>
<p>Fortress products run on open system hardware and software platforms supporting LDAPv3, HTTP/S & Java technologies. Functionality that extend beyond LDAPv3 is realized via OpenLDAP/ApacheDS specific features. With the advent of EnMasse & Commander products, <a href="http://tomcat">Apache Tomcat</a>.apache.org/, or preferred Java servlet container is used to process HTTP communications between endpoints. Fortress provides downloadable packages called QUICKSTARTS which include instructions for first-time install and use of these products.</p>
-<h2 id="what-standards-apply">What standards apply?</h2>
+<h2 id="what-standards-apply">What standards apply?<a class="headerlink" href="#what-standards-apply" title="Permanent link">¶</a></h2>
<p>The following technology standards are applied within Fortress...</p>
-<h3 id="ansi-role-based-access-control-incits-359">ANSI Role-Based Access Control (INCITS 359)</h3>
+<h3 id="ansi-role-based-access-control-incits-359">ANSI Role-Based Access Control (INCITS 359)<a class="headerlink" href="#ansi-role-based-access-control-incits-359" title="Permanent link">¶</a></h3>
<p>There is more to compliance than assigning users to groups and applying ACL policies within directories or databases. <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a> systems provide selective Role activation/deactivation, role hierarchies, and constraints over separation of duty. The <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a> component provides APIs to add, update, delete, and search the directory data. Fortress provides everything that is needed to exploit the full power of this ANSI specification.</p>
<p>More info can be found on <a href="user-guide/1-intro-rbac.html">Intro to ANSI RBAC Page</a></p>
-<h3 id="java-ee-platform-tm-security"><a href="http://java.net/projects/javaee-spec/pages/Home">Java EE Platform</a> (tm) Security</h3>
+<h3 id="java-ee-platform-tm-security"><a href="http://java.net/projects/javaee-spec/pages/Home">Java EE Platform</a> (tm) Security<a class="headerlink" href="#java-ee-platform-tm-security" title="Permanent link">¶</a></h3>
<p>Used for SSL, X.509 mutual authentication, form-based container authentication, coarse-grained authorization, SSO and more. Works within compliant Java Web apps like EnMasse policy server. Java EE security is good because its declarative controls keep the development and integration costs low. At the same time, it provides adequate network system security and the business apps run fast due to caching maintained within the app server container. This reduces costs because of fewer round-trips between the application and policy servers.</p>
-<h3 id="administrative-role-based-access-control-arbac02">Administrative Role-Based Access Control (<a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>)</h3>
+<h3 id="administrative-role-based-access-control-arbac02">Administrative Role-Based Access Control (<a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>)<a class="headerlink" href="#administrative-role-based-access-control-arbac02" title="Permanent link">¶</a></h3>
<p>The ARBAC model explains how <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a> can be extended with organizational controls to govern policies regarding the security administration process. ARBAC helps by allowing administrative tasks be delegated to end users who fall outside typical datacenter operations. Cost savings is realized through lower overhead due to delegation while at same time maintaining a firm grip on compliance.</p>
-<h3 id="ietf-password-policies">IETF Password Policies</h3>
+<h3 id="ietf-password-policies">IETF Password Policies<a class="headerlink" href="#ietf-password-policies" title="Permanent link">¶</a></h3>
<p>OpenLDAP has supported this draft since 2005. Fortress adds by integrating with its administrative and access control APIs. These APIs enable outside apps to participate and manipulate OpenLDAP password policies without understanding the specifics of how they work. Fortress provides services for setting up new policies and ensuring password policies are tracked and enforced across all avenues.</p>
-<h3 id="auditing">Auditing</h3>
+<h3 id="auditing">Auditing<a class="headerlink" href="#auditing" title="Permanent link">¶</a></h3>
<p>Fortress audits use OpenLDAP's slapd access log overlay. This extended capability stores history of slapd events which are needed for replication. The events are persisted in OpenLDAP's back-end database, called the <a href="http://www.openldap.org/pub/hyc/mdm-paper.pdf">Lightning Memory-Mapped DB</a>, or in ApacheDS.</p>
<p>The Fortress audits rely on slapd events to track its data exchanges performed within its own APIs. Change event tracking includes adds, updates, and deletes of Fortress entities. Read and search events tracked include user authentication, authorization, and policy interrogations. Full historical data change tracking is maintained and may be searched later with APIs to be used for monitoring, reporting, and undo. The log may be retrieved later to synch with outside database for long-term regulatory and compliance concerns. </p>
-<h3 id="temporal-constraints">Temporal Constraints</h3>
+<h3 id="temporal-constraints">Temporal Constraints<a class="headerlink" href="#temporal-constraints" title="Permanent link">¶</a></h3>
<p>The Fortress Temporal model allows Users and Roles to carry time and date Constraints which govern when activations may occur. Role constraints are checked on every call into Fortress. The user constraint applied only at session creation.</p>
-<h3 id="ansi-rbac-policy-enhanced-incits-494-2012">ANSI RBAC Policy-Enhanced (INCITS-494-2012)</h3>
+<h3 id="ansi-rbac-policy-enhanced-incits-494-2012">ANSI RBAC Policy-Enhanced (INCITS-494-2012)<a class="headerlink" href="#ansi-rbac-policy-enhanced-incits-494-2012" title="Permanent link">¶</a></h3>
<p>One day.</p>
-<h2 id="what-security-services-are-available">What security services are available?</h2>
+<h2 id="what-security-services-are-available">What security services are available?<a class="headerlink" href="#what-security-services-are-available" title="Permanent link">¶</a></h2>
<p>Over one hundred services divided across the Manager components. Some of them (Access, Admin and Review) map back to <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">ANSI RBAC functional specifications</a>. Others (DelAccess, DelAdmin, DelReview) are for the <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a> model which help manage admnistrative burden for large enterprises. </p>
<p>Each manager component defined below has a specific purpose and contains a collection of related functions to control the Fortress Entities as they pass through its particular area of the identity lifecycle. Of late the APIs have been wrapped with REST by En Masse Policy Server. This allows Fortress functionality to be accessed over HTTP protocol using an XML message format.</p>
<p>A description of the managers follow...</p>
@@ -226,7 +237,7 @@
<li>PswdPolicyMgr - This object adheres to <a href="http://tools.ietf.org/html/draft-behera-ldap-password-policy-10">IETF PW policy draft</a> and is used to perform administrative and review functions on the PWPOLICIES and USERS data sets within Fortress.</li>
<li>ReviewMgr - This interface prescribes the administrative review functions on already provisioned Fortress <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a> entities that reside in LDAP directory to maintain and verify compliance.</li>
</ul>
-<h2 id="where-is-it">Where is it?</h2>
+<h2 id="where-is-it">Where is it?<a class="headerlink" href="#where-is-it" title="Permanent link">¶</a></h2>
<p>Source is managed by Apache's GIT repo:</p>
<ul>
<li><a href="https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git">Fortress Core</a> - RBAC SDK</li>
@@ -234,7 +245,7 @@
<li><a href="https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git">Fortress Rest</a> - RBAC REST Server</li>
<li><a href="https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git">Fortress Realm</a> - RBAC Policy Enforcement Plug-in for Tomcat</li>
</ul>
-<h2 id="what-are-the-conditions">What are the conditions?</h2>
+<h2 id="what-are-the-conditions">What are the conditions?<a class="headerlink" href="#what-are-the-conditions" title="Permanent link">¶</a></h2>
<p>This software development toolkit is open source, thus free to use and distribute under terms of the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License 2.0</a>. It was developed and tested on open systems like <a href="http://www.ubuntu.com/">Ubuntu</a> and <a href="http://www.centos.org/">Centos</a> and was helped along by the following open source products:</p>
<ul>
<li><a href="http://www.openldap.org/project/">The OpenLDAP Project</a></li>
Modified: websites/staging/directory/trunk/content/fortress/user-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide.html Sun Jul 5 22:34:35 2015
@@ -160,11 +160,22 @@
-<h1 id="fortress-users-guide">Fortress User's Guide</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fortress-users-guide">Fortress User's Guide<a class="headerlink" href="#fortress-users-guide" title="Permanent link">¶</a></h1>
<p>This guide is primarily for people new to Fortress. It will guide through the concepts and how to use Fortress.</p>
-<h2 id="about-this-guide">About this guide</h2>
+<h2 id="about-this-guide">About this guide<a class="headerlink" href="#about-this-guide" title="Permanent link">¶</a></h2>
<p>Getting started. Learn how to download and install ApacheDS 2.0 on different platforms, connect to it with various clients (graphical tools among others), manipulate the data within your directory and integrate ApacheDS with other software. The same sample data, provided as a download, is used through the whole guide.</p>
-<h2 id="table-of-contents">Table of contents</h2>
+<h2 id="table-of-contents">Table of contents<a class="headerlink" href="#table-of-contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="user-guide/1-intro-rbac.html">1 - An Introduction to Role-Based Access Control ANSI INCITS 359-2004</a><ul>
<li><a href="user-guide/1.1-rbac-explained.html">1.1 - ANSI RBAC Explained</a></li>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1-intro-rbac.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1-intro-rbac.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1-intro-rbac.html Sun Jul 5 22:34:35 2015
@@ -179,9 +179,20 @@
</div>
-<h1 id="1-an-introduction-to-role-based-access-control-ansi-incits-359-2004">1 - An Introduction to Role-Based Access Control ANSI INCITS 359-2004</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="1-an-introduction-to-role-based-access-control-ansi-incits-359-2004">1 - An Introduction to Role-Based Access Control ANSI INCITS 359-2004<a class="headerlink" href="#1-an-introduction-to-role-based-access-control-ansi-incits-359-2004" title="Permanent link">¶</a></h1>
<p><img alt="ANSI RBAC Specification" src="images/ANSIRBAC-Spec_0.png" /></p>
-<h2 id="table-of-content">Table of content</h2>
+<h2 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="1.1-rbac-explained.html">1.1 - ANSI RBAC Explained</a></li>
<li><a href="1.2-what-is-not-rbac.html">1.2 - What ANSI RBAC is not</a></li>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1.1-rbac-explained.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1.1-rbac-explained.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1.1-rbac-explained.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="11-ansi-rbac-explained">1.1 - ANSI RBAC Explained</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="11-ansi-rbac-explained">1.1 - ANSI RBAC Explained<a class="headerlink" href="#11-ansi-rbac-explained" title="Permanent link">¶</a></h1>
<p><img alt="ANSI RBAC Specification" src="images/ANSIRBAC-Spec_0.png" /></p>
<p>Misnomers abound as to what constitutes a working Role-Based Access Control (RBAC) system. With ANSI RBAC, Groups are not Roles and resource connections not Sessions. This paper explains what ANSI RBAC is and how it can be applied to existing problem domains. It dispels longstanding myths persistent within the enterprise. Additionally readers receive tips on how to implement their own successful RBAC program and where to go to get a fully compliant ANSI RBAC system that may be used as a reference implementation.</p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1.2-what-is-not-rbac.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1.2-what-is-not-rbac.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1.2-what-is-not-rbac.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="12-what-ansi-rbac-is-not">1.2 - What ANSI RBAC is not</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="12-what-ansi-rbac-is-not">1.2 - What ANSI RBAC is not<a class="headerlink" href="#12-what-ansi-rbac-is-not" title="Permanent link">¶</a></h1>
<ul>
<li>
<p>User Groups (i.e. LDAP <em>groupOfUniqueNames</em>). In RBAC, Roles are many-to-many mappings between User and Permission entities. Furthermore the assignments and grants may be interrogated, added or removed at any time. Roles should fall within a hierarchy which facilitate control over assets, encourages reuse and reduces the number of entitlements that have to be maintained.</p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1.3-what-rbac-is.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1.3-what-rbac-is.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1.3-what-rbac-is.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="13-what-ansi-rbac-is">1.3 - What ANSI RBAC is</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="13-what-ansi-rbac-is">1.3 - What ANSI RBAC is<a class="headerlink" href="#13-what-ansi-rbac-is" title="Permanent link">¶</a></h1>
<p>There is more to RBAC than using a Role object during policy enforcement.</p>
<ul>
<li>ANSI INCITS 359-2001, <a href="http://profsandhu.com/journals/tissec/ANSI+INCITS+359-2004.pdf">http://profsandhu.com/journals/tissec/ANSI+INCITS+359-2004.pdf</a> - The ANSI specification describes RBAC and provides functional specifications in Z-notation. </li>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1.4-why-rbac-is-important.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1.4-why-rbac-is-important.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1.4-why-rbac-is-important.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="14-why-is-ansi-rbac-important">1.4 - Why is ANSI RBAC Important?</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="14-why-is-ansi-rbac-important">1.4 - Why is ANSI RBAC Important?<a class="headerlink" href="#14-why-is-ansi-rbac-important" title="Permanent link">¶</a></h1>
<ul>
<li>
<p>Enforces the concept of least privilege. Granting users business functionality doesn't imply entitlements may be used at any time. For example a bank teller shouldn't withdrawal money from customer accounts outside of normal business hours or freelance contractors don't require access to production resources to do their jobs.</p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1.5-how-to-impl-rbac.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1.5-how-to-impl-rbac.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1.5-how-to-impl-rbac.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="15-how-to-implement-ansi-rbac">1.5 - How to implement ANSI RBAC</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="15-how-to-implement-ansi-rbac">1.5 - How to implement ANSI RBAC<a class="headerlink" href="#15-how-to-implement-ansi-rbac" title="Permanent link">¶</a></h1>
<ul>
<li>
<p>Learn using the SPEC</p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/1.6-go-for-more.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/1.6-go-for-more.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/1.6-go-for-more.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="16-where-to-go-for-more-info">1.6 - Where to go for more info</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="16-where-to-go-for-more-info">1.6 - Where to go for more info<a class="headerlink" href="#16-where-to-go-for-more-info" title="Permanent link">¶</a></h1>
<ul>
<li>
<p>Download the ANSI RBAC specification: <a href="http://profsandhu.com/journals/tissec/ANSI+INCITS+359-2004.pdf">http://profsandhu.com/journals/tissec/ANSI+INCITS+359-2004.pdf</a></p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/2-multitenancy.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/2-multitenancy.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/2-multitenancy.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="2-multitenancy">2 - Multitenancy</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="2-multitenancy">2 - Multitenancy<a class="headerlink" href="#2-multitenancy" title="Permanent link">¶</a></h1>
<ul>
<li><a href="2.1-fortress-multitenancy.html">2.1 - Fortress Multitenancy</a></li>
<li><a href="2.2-tradi-multi-instances.html">2.2 - Traditional Multi-Instances architecture</a></li>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/2.1-fortress-multitenancy.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/2.1-fortress-multitenancy.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/2.1-fortress-multitenancy.html Sun Jul 5 22:34:35 2015
@@ -179,12 +179,23 @@
</div>
-<h1 id="21-fortress-multitenancy">2.1 - Fortress Multitenancy</h1>
-<h2 id="multitenancy-defined">Multitenancy Defined</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="21-fortress-multitenancy">2.1 - Fortress Multitenancy<a class="headerlink" href="#21-fortress-multitenancy" title="Permanent link">¶</a></h1>
+<h2 id="multitenancy-defined">Multitenancy Defined<a class="headerlink" href="#multitenancy-defined" title="Permanent link">¶</a></h2>
<p>(From Wikipedia)</p>
<p>Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. With a multitenant architecture, a software application is designed to virtually partition its data and configuration, and each client organization works with a customized virtual application instance.</p>
<p>Multitenancy is also regarded as one of the essential attributes of cloud computing.[1]</p>
-<h2 id="after-fortress">After Fortress</h2>
+<h2 id="after-fortress">After Fortress<a class="headerlink" href="#after-fortress" title="Permanent link">¶</a></h2>
<p>Multi-tenancy allows many clients to share the same ldap infrastructure thus enjoy increased operational efficiency.</p>
<p><img alt="Multitenant Fortress Network Diagram" src="images/multitenant-fortressnetworkdiagram600.png" /></p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html Sun Jul 5 22:34:35 2015
@@ -179,12 +179,23 @@
</div>
-<h1 id="22-traditional-multi-instances-architecture">2.2 - Traditional Multi-Instances architecture</h1>
-<h2 id="multitenancy-defined">Multitenancy Defined</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="22-traditional-multi-instances-architecture">2.2 - Traditional Multi-Instances architecture<a class="headerlink" href="#22-traditional-multi-instances-architecture" title="Permanent link">¶</a></h1>
+<h2 id="multitenancy-defined">Multitenancy Defined<a class="headerlink" href="#multitenancy-defined" title="Permanent link">¶</a></h2>
<p>(From Wikipedia)</p>
<p>Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. With a multitenant architecture, a software application is designed to virtually partition its data and configuration, and each client organization works with a customized virtual application instance.</p>
<p>Multitenancy is also regarded as one of the essential attributes of cloud computing.[1]</p>
-<h2 id="before-fortress">Before Fortress</h2>
+<h2 id="before-fortress">Before Fortress<a class="headerlink" href="#before-fortress" title="Permanent link">¶</a></h2>
<p>Client data had to be maintained on separate instances of LDAP server.</p>
<p><img alt="Multitenancy" src="images/MultiInstance-TraditionalNetworkDiagram2.png" /></p>
Modified: websites/staging/directory/trunk/content/fortress/user-guide/2.3-multitenancy-under-covers.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/2.3-multitenancy-under-covers.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/2.3-multitenancy-under-covers.html Sun Jul 5 22:34:35 2015
@@ -179,8 +179,19 @@
</div>
-<h1 id="23-multitenancy-under-the-covers">2.3 - Multitenancy under the covers</h1>
-<h2 id="under-the-covers">Under the covers</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="23-multitenancy-under-the-covers">2.3 - Multitenancy under the covers<a class="headerlink" href="#23-multitenancy-under-the-covers" title="Permanent link">¶</a></h1>
+<h2 id="under-the-covers">Under the covers<a class="headerlink" href="#under-the-covers" title="Permanent link">¶</a></h2>
<p>The Fortress data design allows clients to share a single server instance because each has its own storage area set aside in the back end database. This increases operational efficiency of the hosting service providerâs data center without sacrificing data isolation on behalf of the clients who use it.</p>
<p><CENTER>
<img alt="" src="images/fortressmultitenantldapschema600.png" />
Modified: websites/staging/directory/trunk/content/fortress/user-guide/3-configuration.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/3-configuration.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/3-configuration.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="31-fortress-configuration">3.1 - Fortress Configuration</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="31-fortress-configuration">3.1 - Fortress Configuration<a class="headerlink" href="#31-fortress-configuration" title="Permanent link">¶</a></h1>
<p>In order to use the API, you must configure it. As it will connect to a remote LDAP server</p>
<p>host=@LDAP_HOST@
port=@LDAP_PORT@
Modified: websites/staging/directory/trunk/content/fortress/vision.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/vision.html (original)
+++ websites/staging/directory/trunk/content/fortress/vision.html Sun Jul 5 22:34:35 2015
@@ -160,12 +160,23 @@
-<h1 id="architectural-vision">Architectural Vision</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="architectural-vision">Architectural Vision<a class="headerlink" href="#architectural-vision" title="Permanent link">¶</a></h1>
<p>Fortress provides a full ANSI RBAC compliant management and enforcement system that builds on existing open source applications like OpenLDAP and Apache Tomcat. It is designed to be both simple to implement and cost effective to maintain.</p>
<p><CENTER>
<IMG src="../../images/Fortress-IAMServer-v2.png" alt="Screenshot"/>
</CENTER></p>
-<h2 id="fortress-server-includes">Fortress Server Includes</h2>
+<h2 id="fortress-server-includes">Fortress Server Includes<a class="headerlink" href="#fortress-server-includes" title="Permanent link">¶</a></h2>
<ul>
<li>Java Servlet container hosting Fortress IAM components</li>
<li>Core APIs are used by items following</li>
@@ -176,7 +187,7 @@
<li>SAML 2.0 B2C SSO</li>
<li>JavaEE Security plug-in (JACC)</li>
</ul>
-<h2 id="openldap-server-includes">OpenLDAP Server Includes</h2>
+<h2 id="openldap-server-includes">OpenLDAP Server Includes<a class="headerlink" href="#openldap-server-includes" title="Permanent link">¶</a></h2>
<ul>
<li>Slapd daemon provides LDAPv3 protocols</li>
<li>Memory Mapped DB (LMDB) and multi-tenant data model</li>
@@ -186,7 +197,7 @@
<li>Virtual Directory caching using slapo cache overlay</li>
<li>Integration with other LDAP servers (AD, ApacheDS, ..)</li>
</ul>
-<h2 id="mysql-server-includes">MySQL Server Includes</h2>
+<h2 id="mysql-server-includes">MySQL Server Includes<a class="headerlink" href="#mysql-server-includes" title="Permanent link">¶</a></h2>
<ul>
<li>Long term audit storage and retrieval</li>
</ul>
Modified: websites/staging/directory/trunk/content/index.html
==============================================================================
--- websites/staging/directory/trunk/content/index.html (original)
+++ websites/staging/directory/trunk/content/index.html Sun Jul 5 22:34:35 2015
@@ -101,7 +101,7 @@
<ul>
<li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./studio/downloads.html">Studio 2.0.0-M9</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
- <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+ <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
<!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -163,14 +163,25 @@
- <p><center>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><center>
<h1>
The Apache Directory™ Project
</h1>
</center> </p>
-<h2 id="project-vision">Project Vision</h2>
+<h2 id="project-vision">Project Vision<a class="headerlink" href="#project-vision" title="Permanent link">¶</a></h2>
<p>We strive to increase LDAP awareness, comfort and adoption to bring forth what we call the Modern LDAP Renaissance. Learn more about our vision <a href="http://directory.apache.org/vision.html">here</a></p>
-<h2 id="directory-sub-projects">Directory Sub-Projects</h2>
+<h2 id="directory-sub-projects">Directory Sub-Projects<a class="headerlink" href="#directory-sub-projects" title="Permanent link">¶</a></h2>
<p>The Apache Directory Project provides directory solutions entirely written in Java. These include a directory server, which has been certified as LDAP v3 compliant by the Open Group (ApacheDS), and Eclipse-based directory tools (Apache Directory Studio).</p>
<STYLE type="text/css">
.separator {height: 10px;}
@@ -205,7 +216,7 @@ td {font-size: 12px;}
<!-- Apache LDAP API project -->
<td style="border-width: 0; border-right: 1px solid silver; padding-right: 15px; width:50%;" valign="top">
<div class="download-link">
- <a href="./../api/downloads.html" class="download_badge_api"><b>Download Apache<br>LDAP API 1.0.0-M30</b></a>
+ <a href="./../api/downloads.html" class="download_badge_api"><b>Download Apache<br>LDAP API 1.0.0-M31</b></a>
</div>
<div class="separator"> </div>
Modified: websites/staging/directory/trunk/content/issue-tracking.html
==============================================================================
--- websites/staging/directory/trunk/content/issue-tracking.html (original)
+++ websites/staging/directory/trunk/content/issue-tracking.html Sun Jul 5 22:34:35 2015
@@ -101,7 +101,7 @@
<ul>
<li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./studio/downloads.html">Studio 2.0.0-M9</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
- <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+ <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
<!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,7 +162,18 @@
-<h1 id="issue-tracking">Issue Tracking</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="issue-tracking">Issue Tracking<a class="headerlink" href="#issue-tracking" title="Permanent link">¶</a></h1>
<p>Our project uses <a href="http://www.atlassian.com/software/jira">JIRA</a>, a Java EE based issue tracking and project management application.</p>
<p><img alt="JIRA" src="images/jira-space-logo.gif" /></p>
<p>Issues, bugs, and feature requests should be submitted to the following issue tracking system.</p>
Modified: websites/staging/directory/trunk/content/kerby/downloads.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/downloads.html (original)
+++ websites/staging/directory/trunk/content/kerby/downloads.html Sun Jul 5 22:34:35 2015
@@ -156,14 +156,25 @@
-<h1 id="downloads">Downloads</h1>
-<h2 id="jar-download">Jar Download</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="downloads">Downloads<a class="headerlink" href="#downloads" title="Permanent link">¶</a></h1>
+<h2 id="jar-download">Jar Download<a class="headerlink" href="#jar-download" title="Permanent link">¶</a></h2>
<p>The Apache Kerby is distributed as a jar.</p>
<ul>
<li><img alt="Download" src="../images/download-archive.png" /> <a href="download/download-archive.html">Download Archive zip/tar.gz</a></li>
<li><img alt="Download" src="../images/download-sources.png" /> <a href="download/download-sources.html">Download Sources</a></li>
</ul>
-<h2 id="maven-dependency">Maven Dependency</h2>
+<h2 id="maven-dependency">Maven Dependency<a class="headerlink" href="#maven-dependency" title="Permanent link">¶</a></h2>
<p>The Apache Kerby is also available as a Maven dependency:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.directory.kerby<span class="nt"></groupId></span>
Modified: websites/staging/directory/trunk/content/kerby/index.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/index.html (original)
+++ websites/staging/directory/trunk/content/kerby/index.html Sun Jul 5 22:34:35 2015
@@ -167,7 +167,7 @@
Apache Kerby, or simply <em>Kerby</em>, is a Kerbeors server implementation, in Java, plus a set of associated tools.<br/>
</div>
<!--div class="download-link">
- <a href="./../api/downloads.html" class="download_badge"><b>Download Apache<br>LDAP API 1.0.0-M30</b></a>
+ <a href="./../api/downloads.html" class="download_badge"><b>Download Apache<br>LDAP API 1.0.0-M31</b></a>
</div-->
</div>
<!--div class="right">
@@ -177,7 +177,18 @@
- <div class="news"><h1 id="news">News</h1>
+ <div class="news"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="news">News<a class="headerlink" href="#news" title="Permanent link">¶</a></h1>
<p>No news...</p></div>
Modified: websites/staging/directory/trunk/content/kerby/issues.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/issues.html (original)
+++ websites/staging/directory/trunk/content/kerby/issues.html Sun Jul 5 22:34:35 2015
@@ -156,7 +156,18 @@
-<h1 id="kerby-issue-tracking">Kerby Issue tracking</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="kerby-issue-tracking">Kerby Issue tracking<a class="headerlink" href="#kerby-issue-tracking" title="Permanent link">¶</a></h1>
<p>Our project uses <a href="https://issues.apache.org/jira/browse/DIRKRB/">JIRA</a>, a Java EE based issue tracking and project management application.</p>
<p><img alt="JIRA" src="../images/jira-space-logo.gif" /></p>
<p>Issues, bugs, and feature requests should be submitted to the following issue tracking system :</p>
Modified: websites/staging/directory/trunk/content/kerby/news.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/news.html (original)
+++ websites/staging/directory/trunk/content/kerby/news.html Sun Jul 5 22:34:35 2015
@@ -156,7 +156,18 @@
-<h1 id="news">News</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="news">News<a class="headerlink" href="#news" title="Permanent link">¶</a></h1>
<p>No news...</p>
Modified: websites/staging/directory/trunk/content/kerby/overview.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/overview.html (original)
+++ websites/staging/directory/trunk/content/kerby/overview.html Sun Jul 5 22:34:35 2015
@@ -156,9 +156,20 @@
-<h1 id="kerby-overview">Kerby Overview</h1>
-<h2 id="rationale">Rationale</h2>
-<h2 id="what-is-it">What is it?</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="kerby-overview">Kerby Overview<a class="headerlink" href="#kerby-overview" title="Permanent link">¶</a></h1>
+<h2 id="rationale">Rationale<a class="headerlink" href="#rationale" title="Permanent link">¶</a></h2>
+<h2 id="what-is-it">What is it?<a class="headerlink" href="#what-is-it" title="Permanent link">¶</a></h2>
Modified: websites/staging/directory/trunk/content/kerby/quick-start.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/quick-start.html (original)
+++ websites/staging/directory/trunk/content/kerby/quick-start.html Sun Jul 5 22:34:35 2015
@@ -156,7 +156,18 @@
-<h1 id="kerby-quick-start-guides">Kerby Quick-start guides</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="kerby-quick-start-guides">Kerby Quick-start guides<a class="headerlink" href="#kerby-quick-start-guides" title="Permanent link">¶</a></h1>
<p>The Quick Start guides show you how to do base install of Kerby:</p>
Modified: websites/staging/directory/trunk/content/kerby/user-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/user-guide.html (original)
+++ websites/staging/directory/trunk/content/kerby/user-guide.html Sun Jul 5 22:34:35 2015
@@ -156,10 +156,21 @@
-<h1 id="kerby-users-guide">Kerby User's Guide</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="kerby-users-guide">Kerby User's Guide<a class="headerlink" href="#kerby-users-guide" title="Permanent link">¶</a></h1>
<p>This guide is primarily for people new to Kerby. It will guide through the concepts and how to use Kerby.</p>
-<h2 id="about-this-guide">About this guide</h2>
-<h2 id="table-of-contents">Table of contents</h2>
+<h2 id="about-this-guide">About this guide<a class="headerlink" href="#about-this-guide" title="Permanent link">¶</a></h2>
+<h2 id="table-of-contents">Table of contents<a class="headerlink" href="#table-of-contents" title="Permanent link">¶</a></h2>
Modified: websites/staging/directory/trunk/content/kerby/vision.html
==============================================================================
--- websites/staging/directory/trunk/content/kerby/vision.html (original)
+++ websites/staging/directory/trunk/content/kerby/vision.html Sun Jul 5 22:34:35 2015
@@ -156,7 +156,18 @@
-<h1 id="vision">Vision</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="vision">Vision<a class="headerlink" href="#vision" title="Permanent link">¶</a></h1>
<p>Kerby is a Kerberos Server implementation written in Java.</p>
Modified: websites/staging/directory/trunk/content/mailing-lists-and-irc.html
==============================================================================
--- websites/staging/directory/trunk/content/mailing-lists-and-irc.html (original)
+++ websites/staging/directory/trunk/content/mailing-lists-and-irc.html Sun Jul 5 22:34:35 2015
@@ -101,7 +101,7 @@
<ul>
<li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./studio/downloads.html">Studio 2.0.0-M9</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
- <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+ <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
<li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
<!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a> <IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,8 +162,19 @@
-<h1 id="mailing-lists-and-irc">Mailing lists and IRC</h1>
-<h2 id="mailing-list-etiquette">Mailing list etiquette</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="mailing-lists-and-irc">Mailing lists and IRC<a class="headerlink" href="#mailing-lists-and-irc" title="Permanent link">¶</a></h1>
+<h2 id="mailing-list-etiquette">Mailing list etiquette<a class="headerlink" href="#mailing-list-etiquette" title="Permanent link">¶</a></h2>
<p>Please consider the following before posting Emails to the lists:</p>
<ul>
<li>No posts with html.</li>
@@ -183,7 +194,7 @@
</li>
</ul>
<p>An article by Eric Steven Raymond very worth reading is found here: <a href="http://www.catb.org/esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</a>.</p>
-<h2 id="project-mailing-lists">Project mailing lists</h2>
+<h2 id="project-mailing-lists">Project mailing lists<a class="headerlink" href="#project-mailing-lists" title="Permanent link">¶</a></h2>
<p>These are the mailing lists that have been established for this project. We haven't a distinguished mailing list for each of the sub-projects : if you have questions about Escimo, Mavibot or ApacheDS, for instance, you have to use the Directory Users or Developpers mailing list.</p>
<p>For each list, there is a subscribe, unsubscribe, and an archive link:</p>
<table>
@@ -241,7 +252,7 @@
</tr>
</tbody>
</table>
-<h2 id="irc-channels">IRC channels</h2>
+<h2 id="irc-channels">IRC channels<a class="headerlink" href="#irc-channels" title="Permanent link">¶</a></h2>
<ul>
<li>Users IRC channel: <a href="irc://irc.freenode.net/apache-directory">#apache-directory @ irc://irc.freenode.net</a> </li>
<li>Developers IRC channel: <a href="irc://irc.freenode.net/apache-directory-dev">#apache-directory-dev @ irc://irc.freenode.net</a> </li>
Modified: websites/staging/directory/trunk/content/mavibot/coding-standards.html
==============================================================================
--- websites/staging/directory/trunk/content/mavibot/coding-standards.html (original)
+++ websites/staging/directory/trunk/content/mavibot/coding-standards.html Sun Jul 5 22:34:35 2015
@@ -152,14 +152,25 @@
-<h1 id="mavibot-coding-standards">Mavibot Coding Standards</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="mavibot-coding-standards">Mavibot Coding Standards<a class="headerlink" href="#mavibot-coding-standards" title="Permanent link">¶</a></h1>
<p>Welcome to you, developer ! You have been elected committer on the project, or you want to contribute some code or some patch? This is great news. However, in order to be able to share your 'vision' and your code, some rules must be followed.</p>
<p>Hey, remember that those rules are not the best nor the worst, they are pretty much what they are for historical reasons, or for technical reasons, however, please, accept them as they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using spaces instead of tab ??? How stupid is this rule etc etc.) Rules are <em><em>alway</em>s</em> stupid, but smart people follow them ;)</p>
<p><strong>eclipse IDE</strong></p>
<p>Eclipse users can import those two files to enforce the code formating : <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/formatting.xml">formatting.xml</a> and <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/codetemplates.xml">codetemplates.xml</a></p>
<p><strong>IDEA IDE</strong></p>
<p>IDEA users can import <a href="settings.jar">this file</a> to enforce the code formating.</p>
-<h2 id="headers">Headers</h2>
+<h2 id="headers">Headers<a class="headerlink" href="#headers" title="Permanent link">¶</a></h2>
<p>First, you <strong>must</strong> (and this rule accept no exception) use this header in top of all source file, or each file in which you can have comments :</p>
<div class="codehilite"><pre><span class="cm">/*</span>
<span class="cm"> * Licensed to the Apache Software Foundation (ASF) under one</span>
@@ -183,13 +194,11 @@
</pre></div>
-<h3 id="classinterface-headers">Class/Interface headers</h3>
+<h3 id="classinterface-headers">Class/Interface headers<a class="headerlink" href="#classinterface-headers" title="Permanent link">¶</a></h3>
<p>Each <strong>Class</strong> or <em>Interface</em> should have an header which must contains :</p>
<ul>
<li>A description of this class/interface</li>
-<li>
-<p>an <em>author</em> tag which should be :</p>
-<div class="codehilite"><pre><span class="nd">@author</span> <span class="o"><</span><span class="n">a</span> <span class="n">href</span><span class="o">=</span><span class="s">"mailto:dev@directory.apache.org"</span><span class="o">></span><span class="n">Apache</span> <span class="n">Directory</span> <span class="n">Project</span><span class="o"></</span><span class="n">a</span><span class="o">></span>
+<li>an <em>author</em> tag which should be :<div class="codehilite"><pre><span class="nd">@author</span> <span class="o"><</span><span class="n">a</span> <span class="n">href</span><span class="o">=</span><span class="s">"mailto:dev@directory.apache.org"</span><span class="o">></span><span class="n">Apache</span> <span class="n">Directory</span> <span class="n">Project</span><span class="o"></</span><span class="n">a</span><span class="o">></span>
</pre></div>
@@ -200,12 +209,12 @@ Thanks to avoid to put your name. The co
</DIV>
<p>If you use <strong>html</strong> tags, remember to escape '<' and '>' characters...</p>
-<h3 id="static-members-and-other-members">Static members and other members</h3>
+<h3 id="static-members-and-other-members">Static members and other members<a class="headerlink" href="#static-members-and-other-members" title="Permanent link">¶</a></h3>
<p>Just add a single line javadoc comment like : <em>/*<em> blah ... </em>/</em> before each member</p>
-<h3 id="methods">Methods</h3>
+<h3 id="methods">Methods<a class="headerlink" href="#methods" title="Permanent link">¶</a></h3>
<p>Follow the standard <strong>javadoc</strong> rules : Description, <strong>@param</strong>, <strong>@exception</strong> and <strong>@return</strong>. It should be enough. Avoid <strong>@tags</strong>, <strong>@todo</strong> tags, etc...</p>
<p>Escape <strong>html</strong> characters</p>
-<h2 id="comments">Comments</h2>
+<h2 id="comments">Comments<a class="headerlink" href="#comments" title="Permanent link">¶</a></h2>
<p>No special rules, except that you should avoid :</p>
<ul>
<li>Useless comments like : i++; /* Increment i */</li>
@@ -214,7 +223,7 @@ Thanks to avoid to put your name. The co
<li>Dead code commented. If it's dead, then put it in a coffin. We use SVN, the Ressuscitator !</li>
</ul>
<p>Basically, use your common sense :-)</p>
-<h2 id="naming">Naming</h2>
+<h2 id="naming">Naming<a class="headerlink" href="#naming" title="Permanent link">¶</a></h2>
<p>Naming ! Sounds like Blaming :-). Ok. We use <strong>Sun(tm/c/r)</strong> style :</p>
<ul>
<li>Constants are in UPPER CASE with accepted '_'</li>
@@ -228,13 +237,13 @@ Thanks to avoid to put your name. The co
</ul>
<p>If you browse the code, you will see that many classes does not respect those rules. That's life ! Don't fix it if you don't touch a class. If you are fixing a method in a class, then you can change the code to respect the rules. Little by little, we may reach a stable state where all the code respect the rules ;)</p>
<p>Naming is really important for <strong>APIs</strong>. Be smart. If you are not sure, ask.</p>
-<h2 id="spaces-vs-tabs">Spaces vs tabs</h2>
+<h2 id="spaces-vs-tabs">Spaces vs tabs<a class="headerlink" href="#spaces-vs-tabs" title="Permanent link">¶</a></h2>
<DIV class="warning" markdown="1">
**FOUR SPACES, NO TAB. Final.**
</DIV>
<p>No discussion. Using tabs break diffs. Modify your <strong>IDE</strong> to insert spaces when you use tabs, before it saves the file.</p>
-<h2 id="formatting">Formatting</h2>
+<h2 id="formatting">Formatting<a class="headerlink" href="#formatting" title="Permanent link">¶</a></h2>
<p>Use the <strong>formatting.xml</strong> file which can be found in the <strong>resources</strong> directory in the root of the project. This is for <em>Eclipse</em>. If you don't use eclipse, then translate the formating to your favorite <strong>IDE</strong>.</p>
<p>Use the <strong>codetemplates.xml</strong> file if you are using <em>Eclipse</em> too. You will find it at the same location. It brings you some standard headers for new classes, nex methods, etc.</p>
<p>Use <strong>UTF-8</strong> as a default for your files (except for properties, thanks to <strong>java</strong>, which should be in <strong>ISO-8859-1</strong>). Forget about exotic encoding...</p>
@@ -265,9 +274,9 @@ Thanks to avoid to put your name. The co
</pre></div>
-<h2 id="imports">Imports</h2>
+<h2 id="imports">Imports<a class="headerlink" href="#imports" title="Permanent link">¶</a></h2>
<p>Always declare all the classes you import, do not use <strong>x.y.*</strong></p>
-<h2 id="what-else">What else ?</h2>
+<h2 id="what-else">What else ?<a class="headerlink" href="#what-else" title="Permanent link">¶</a></h2>
<p>Well, this was a very short introduction about coding rules. Use common sense, look at what you see around you when adding some code, ask people about format, if you have a question.</p>
<p>That's it ! (I wait your comments, guys :-)</p>
Modified: websites/staging/directory/trunk/content/mavibot/developer-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/mavibot/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/mavibot/developer-guide.html Sun Jul 5 22:34:35 2015
@@ -152,7 +152,18 @@
-<h1 id="mavibot-developers-guide">Mavibot Developers Guide</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="mavibot-developers-guide">Mavibot Developers Guide<a class="headerlink" href="#mavibot-developers-guide" title="Permanent link">¶</a></h1>
<p>We will describe how to get the code, build it, and release it.</p>
<div class="toc">
<ul>
@@ -195,8 +206,8 @@
</li>
</ul>
</div>
-<h2 id="getting-the-source-building-the-trunks">Getting the source, Building the trunks</h2>
-<h3 id="prerequisites-for-building">Prerequisites for building</h3>
+<h2 id="getting-the-source-building-the-trunks">Getting the source, Building the trunks<a class="headerlink" href="#getting-the-source-building-the-trunks" title="Permanent link">¶</a></h2>
+<h3 id="prerequisites-for-building">Prerequisites for building<a class="headerlink" href="#prerequisites-for-building" title="Permanent link">¶</a></h3>
<p>You must have installed <strong>Maven 3.0.4</strong> and have a <strong>JDK 7</strong> installed on your computer. A working internet connection is also mandatory, unless you have all the needed dependences and plugins loaded locally.</p>
<DIV class="note" markdown="1">
If the build hangs or you get an out of memory exception please increase the heap space:
@@ -211,7 +222,7 @@ If the build hangs or you get an out of
mvn clean install
</DIV>
-<h3 id="maven">Maven</h3>
+<h3 id="maven">Maven<a class="headerlink" href="#maven" title="Permanent link">¶</a></h3>
<p><a href="http://maven.apache.org/download.html">Download</a> and install Maven 3.0.4.</p>
<p>Add a MAVEN_HOME environment variable and add MAVEN_HOME/bin to your system path:</p>
<p>On a Linux box you could add the following to the .bashrc file (.bashrc is a file you'll find in your home directory)</p>
@@ -223,13 +234,13 @@ If the build hangs or you get an out of
<p>Windows users, use Control Panel -> System -> Advanced -> Environment Variables</p>
-<h3 id="jdk-7">JDK 7</h3>
+<h3 id="jdk-7">JDK 7<a class="headerlink" href="#jdk-7" title="Permanent link">¶</a></h3>
<DIV class="note" markdown="1">
We recommend using a version >= 1.7
</DIV>
<p>Any newer version should also work.</p>
-<h2 id="getting-the-code">Getting the code</h2>
+<h2 id="getting-the-code">Getting the code<a class="headerlink" href="#getting-the-code" title="Permanent link">¶</a></h2>
<p>To download the sources from trunk, you must have installed a <strong>Subversion</strong> client.</p>
<p>With readonly access :</p>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">mavibot</span><span class="o">/</span><span class="n">trunk</span> <span class="n">mavibot</span><span class="o">-</span><span class="n">trunk</span>
@@ -241,14 +252,14 @@ We recommend using a version >= 1.7
</pre></div>
-<h2 id="building-the-trunk">Building the trunk</h2>
+<h2 id="building-the-trunk">Building the trunk<a class="headerlink" href="#building-the-trunk" title="Permanent link">¶</a></h2>
<p>You may either specify the profile at the command-line, each time you use 'mvn', or you may configure the profile to always be active.</p>
<p>To use a profile at the command-line:</p>
<div class="codehilite"><pre><span class="c"># mvn [-P<profile>] [options] [<goal(s)>] [<phase(s)>]</span>
</pre></div>
-<h3 id="building-the-trunk-for-real">Building the trunk, for real</h3>
+<h3 id="building-the-trunk-for-real">Building the trunk, for real<a class="headerlink" href="#building-the-trunk-for-real" title="Permanent link">¶</a></h3>
<p>Now, we can compile the projects.</p>
<p>The command is simple :</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">mavibot</span><span class="o">-</span><span class="n">trunk</span>
@@ -269,19 +280,19 @@ We recommend using a version >= 1.7
<p>That's it, the jars will be find in target/mavibot-1.0.0-M?-<XXXXXX>-setup.jar where XXXXXX is your local system and M? is the milestone release number for the 1.0 branch.</p>
-<h2 id="eclipse">Eclipse</h2>
+<h2 id="eclipse">Eclipse<a class="headerlink" href="#eclipse" title="Permanent link">¶</a></h2>
<p>We use Eclipse extensively, so these chapters, byt any other idea would be ok too.</p>
-<h3 id="building-eclipse-files">Building eclipse files</h3>
+<h3 id="building-eclipse-files">Building eclipse files<a class="headerlink" href="#building-eclipse-files" title="Permanent link">¶</a></h3>
<p>To build the .project and .classpath files for eclipse, type the following commands :</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">mavibot</span><span class="o">-</span><span class="n">trunk</span>
<span class="n">mvn</span> <span class="n">eclipse</span><span class="p">:</span><span class="n">eclipse</span>
</pre></div>
-<h3 id="maven-settings">Maven settings</h3>
+<h3 id="maven-settings">Maven settings<a class="headerlink" href="#maven-settings" title="Permanent link">¶</a></h3>
<p>Don't forget to declare a classpath variable named M2_REPO, pointing to ~/.m2/repository, otherwise many links to existing jars will be broken.</p>
<p>You can declare new variables in Eclipse in <em>Windows -> Preferences...</em> and selecting <em>Java -> Build Path -> Classpath Variables</em></p>
-<h2 id="coding-standards">Coding standards</h2>
+<h2 id="coding-standards">Coding standards<a class="headerlink" href="#coding-standards" title="Permanent link">¶</a></h2>
<p>The applicable coding standards for Mavibot are described in <a href="coding-standards.html">Coding Standards</a></p>
<p>There are some more rules, as we are using <strong>Java 7</strong> now :</p>
<ul>
@@ -290,9 +301,9 @@ We recommend using a version >= 1.7
<li>Use <strong>assert</strong>. It's usefull, especially instead of a bunch of <strong>if (<test is wrong>)</strong> then throw Exception* when controlling incoming parameters</li>
<li>Use the new <em>Enum</em> type !</li>
</ul>
-<h1 id="releasing-mavibot">Releasing Mavibot</h1>
+<h1 id="releasing-mavibot">Releasing Mavibot<a class="headerlink" href="#releasing-mavibot" title="Permanent link">¶</a></h1>
<p>Since we are using Nexus for releases the release process is as follows (see also <a href="publishing-maven-artifacts.html">http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven</a>).</p>
-<h2 id="test-the-project">Test the Project</h2>
+<h2 id="test-the-project">Test the Project<a class="headerlink" href="#test-the-project" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ mvn release:prepare -DdryRun=true
</pre></div>
@@ -311,27 +322,27 @@ What is the new development version for
<p>Here, we just validated the proposed versions.</p>
-<h2 id="deploy-a-snapshot">Deploy a Snapshot</h2>
+<h2 id="deploy-a-snapshot">Deploy a Snapshot<a class="headerlink" href="#deploy-a-snapshot" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ mvn deploy
</pre></div>
<p>This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key)</p>
-<h2 id="prepare-the-release">Prepare the Release</h2>
+<h2 id="prepare-the-release">Prepare the Release<a class="headerlink" href="#prepare-the-release" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ mvn release:clean
$ mvn release:prepare
</pre></div>
<p>This creates a tag here: http://svn.apache.org/viewvc/directory/mavibot/tags/</p>
-<h2 id="stage-the-release">Stage the Release</h2>
+<h2 id="stage-the-release">Stage the Release<a class="headerlink" href="#stage-the-release" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ mvn release:perform
</pre></div>
<p>This deploys the release to a staging repository.</p>
<p>Go to <a href="https://repository.apache.org/index.html#stagingRepositories">https://repository.apache.org/index.html#stagingRepositories</a> and close the staging repository.</p>
-<h2 id="build-the-site">Build the Site</h2>
+<h2 id="build-the-site">Build the Site<a class="headerlink" href="#build-the-site" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ cd target/checkout
$ mvn site
</pre></div>
@@ -345,7 +356,7 @@ $ mvn site
</pre></div>
-<h2 id="publish-source-and-binary-distribution-packages">Publish Source and Binary Distribution Packages</h2>
+<h2 id="publish-source-and-binary-distribution-packages">Publish Source and Binary Distribution Packages<a class="headerlink" href="#publish-source-and-binary-distribution-packages" title="Permanent link">¶</a></h2>
<p>First of all, create a new directory on people.apache.org/public_html to store the pacckages :</p>
<div class="codehilite"><pre>$ ssh people.apache.org
$ mkdir public_html/mavibot-<version>
@@ -384,7 +395,7 @@ $ scp mavibot-<version>-* people.a
</pre></div>
-<h2 id="vote">Vote</h2>
+<h2 id="vote">Vote<a class="headerlink" href="#vote" title="Permanent link">¶</a></h2>
<p>Start a 72h vote at the dev mailing list.</p>
<p>Here is an exemple of a mote mail :</p>
<div class="codehilite"><pre>Hi !
@@ -432,7 +443,7 @@ Emmanuel
</pre></div>
-<h2 id="release">Release</h2>
+<h2 id="release">Release<a class="headerlink" href="#release" title="Permanent link">¶</a></h2>
<p>If the vote succeeds the Mavibot project can be released.</p>
<p>Go to <a href="https://repository.apache.org/index.html#stagingRepositories">https://repository.apache.org/index.html#stagingRepositories</a> and release the staging repository so all artifacts are published to Maven central.</p>
<p>Move the distribution packages (sources and binaries) to the dist SVN repository: </p>
@@ -457,7 +468,7 @@ $
<p>The packages should now be available on <strong>http://www.us.apache.org/dist/directory/mavibot/dist/<version></strong></p>
-<h2 id="deploy-the-javadocs-and-xref">Deploy the Javadocs and XRef</h2>
+<h2 id="deploy-the-javadocs-and-xref">Deploy the Javadocs and XRef<a class="headerlink" href="#deploy-the-javadocs-and-xref" title="Permanent link">¶</a></h2>
<p>We now can deploy the generated Javadoc and cross-reference pages. They are generated in the following directory :</p>
<div class="codehilite"><pre>target/checkout/target/site
</pre></div>
@@ -469,7 +480,7 @@ xref
</pre></div>
-<h3 id="staging-or-production">Staging or Production?</h3>
+<h3 id="staging-or-production">Staging or Production?<a class="headerlink" href="#staging-or-production" title="Permanent link">¶</a></h3>
<p>Those files will be stored on the production server only !!! And some extra caution must be taken not to delete them when we will publish the staging site too...</p>
<p>First of all, you must checkout the two CMS store for the site : staging and revision.</p>
<div class="codehilite"><pre>$ cd ~/apacheds
@@ -534,7 +545,7 @@ RewriteRule ^latest/(.*)$ <version>
<p>Save and commit the file.</p>
-<h2 id="update-the-web-site">Update the web site</h2>
+<h2 id="update-the-web-site">Update the web site<a class="headerlink" href="#update-the-web-site" title="Permanent link">¶</a></h2>
<p>You can now update the site, add a news on the front page, and publish the site.</p>
<p>There are a few places to modify :
- /lib/path.pm : update the $version_mavibot variable with the new version.
@@ -542,7 +553,7 @@ RewriteRule ^latest/(.*)$ <version>
- /content/mavibot/news.mdtext : add the news on top of thise page
- /content/mavibot/download-old-versions.mdtext : add a new line on top of the array, which refers to the latest version before the new one</p>
<p>Commit the changes, and publish the web site, you are done !</p>
-<h2 id="inform-the-world">Inform the world !</h2>
+<h2 id="inform-the-world">Inform the world !<a class="headerlink" href="#inform-the-world" title="Permanent link">¶</a></h2>
<p>After 24h, you can now inform the world about the release.</p>
<p>Send a mail to the users and dev mailing list, and one to the announce@apache.org list.</p>
<p>You are done !</p>
Modified: websites/staging/directory/trunk/content/mavibot/download-old-versions.html
==============================================================================
--- websites/staging/directory/trunk/content/mavibot/download-old-versions.html (original)
+++ websites/staging/directory/trunk/content/mavibot/download-old-versions.html Sun Jul 5 22:34:35 2015
@@ -152,7 +152,18 @@
-<h1 id="download-old-versions">Download Old Versions</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="download-old-versions">Download Old Versions<a class="headerlink" href="#download-old-versions" title="Permanent link">¶</a></h1>
<p><CENTER></p>
<table>
<thead>
@@ -210,7 +221,7 @@ We encourage you to verify the integrity
* the MD5 file (checksum).
</DIV>
-<h2 id="verify-the-integrity-of-the-file">Verify the integrity of the file</h2>
+<h2 id="verify-the-integrity-of-the-file">Verify the integrity of the file<a class="headerlink" href="#verify-the-integrity-of-the-file" title="Permanent link">¶</a></h2>
<p>The PGP signatures can be verified using PGP or GPG. First download the <a href="http://www.apache.org/dist/directory/KEYS">keys</a> file as well as the asc signature file for the relevant distribution. Then verify the signatures using:</p>
<div class="codehilite"><pre>$ <span class="n">pgpk</span> <span class="o">-</span><span class="n">a</span> <span class="n">KEYS</span>
$ <span class="n">pgpv</span> <span class="n">apache_1</span><span class="p">.</span>3<span class="p">.</span>24<span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span><span class="p">.</span><span class="n">asc</span>
@@ -229,7 +240,7 @@ $ <span class="n">gpg</span> <span class
</pre></div>
-<p>Alternatively, you can verify the MD5 signature on the files. A unix program called md5 or md5sum is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/],%20or%20[here|http://www.slavasoft.com/fsum/">here</a>.</p>
+<p>Alternatively, you can verify the MD5 signature on the files. A unix program called md5 or md5sum is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/], or [here|http://www.slavasoft.com/fsum/">here</a>.</p>
Modified: websites/staging/directory/trunk/content/mavibot/downloads.html
==============================================================================
--- websites/staging/directory/trunk/content/mavibot/downloads.html (original)
+++ websites/staging/directory/trunk/content/mavibot/downloads.html Sun Jul 5 22:34:35 2015
@@ -152,14 +152,25 @@
-<h1 id="downloads">Downloads</h1>
-<h2 id="jar-download">Jar Download</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="downloads">Downloads<a class="headerlink" href="#downloads" title="Permanent link">¶</a></h1>
+<h2 id="jar-download">Jar Download<a class="headerlink" href="#jar-download" title="Permanent link">¶</a></h2>
<p>The Apache Mavibot package is distributed as a jar.</p>
<ul>
<li><img alt="Download" src="../images/download-archive.png" /> <a href="download/download-archive.html">Download Archive zip/tar.gz</a></li>
<li><img alt="Download" src="../images/download-sources.png" /> <a href="download/download-sources.html">Download Sources</a></li>
</ul>
-<h2 id="maven-dependency">Maven Dependency</h2>
+<h2 id="maven-dependency">Maven Dependency<a class="headerlink" href="#maven-dependency" title="Permanent link">¶</a></h2>
<p>The Apache Mavibot package is also available as a Maven dependency:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.directory.mavibot<span class="nt"></groupId></span>