Updated the various menu to show the server side password hash feature. Added a LDIF modify example for this feature

diff --git a/source/apacheds/advanced-ug/4-authentication-and-authorization.md b/source/apacheds/advanced-ug/4-authentication-and-authorization.md
index 2177c5d..f390dc9 100644
--- a/source/apacheds/advanced-ug/4-authentication-and-authorization.md
+++ b/source/apacheds/advanced-ug/4-authentication-and-authorization.md

@@ -17,6 +17,7 @@
         * [4.1.1.1 - Anonymous Authentication](4.1.1.1-anonymous-authn.html)
         * [4.1.1.2 - Name/Password Authentication](4.1.1.2-name-password-authn.html)
         * [4.1.1.3 - Unauthenticated Authentication](4.1.1.3-unauthenticated-authn.html)
+        * [4.1.1.4 - Server side password hashing](advanced-ug/4.1.1.4-ss-password-hash.html)
     * [4.1.2 - SASL authentication](4.1.2-sasl-authn.html)
         * [4.1.2.1 - SASL PLAIN text Authentication](4.1.2.1-sasl-plain-text-authn.html)
         * [4.1.2.2 - SASL CRAM-MD5 Authentication](4.1.2.2-sasl-cram-md5-authn.html)

diff --git a/source/apacheds/advanced-ug/4.1-authentication.md b/source/apacheds/advanced-ug/4.1-authentication.md
index edcd56c..57eb92a 100644
--- a/source/apacheds/advanced-ug/4.1-authentication.md
+++ b/source/apacheds/advanced-ug/4.1-authentication.md

@@ -16,6 +16,7 @@
     * [4.1.1.1 - Anonymous Authentication](4.1.1.1-anonymous-authn.html)
     * [4.1.1.2 - Name/Password Authentication](4.1.1.2-name-password-authn.html)
     * [4.1.1.3 - Unauthenticated Authentication](4.1.1.3-unauthenticated-authn.html)
+    * [4.1.1.4 - Server side password hashing](advanced-ug/4.1.1.4-ss-password-hash.html)
 * [4.1.2 - SASL authentication](4.1.2-sasl-authn.html)
     * [4.1.2.1 - SASL PLAIN text Authentication](4.1.2.1-sasl-plain-text-authn.html)
     * [4.1.2.2 - SASL CRAM-MD5 Authentication](4.1.2.2-sasl-cram-md5-authn.html)

diff --git a/source/apacheds/advanced-ug/4.1.1-simple-authn.md b/source/apacheds/advanced-ug/4.1.1-simple-authn.md
index a6c65fb..81c32bc 100644
--- a/source/apacheds/advanced-ug/4.1.1-simple-authn.md
+++ b/source/apacheds/advanced-ug/4.1.1-simple-authn.md

@@ -17,6 +17,7 @@
   * [4.1.1.1 - Anonymous Authentication](4.1.1.1-anonymous-authn.html)
   * [4.1.1.2 - Name/Password Authentication](4.1.1.2-name-password-authn.html)
   * [4.1.1.3 - Unauthenticated Authentication](4.1.1.3-unauthenticated-authn.html)
+  * [4.1.1.4 - Server side password hashing](advanced-ug/4.1.1.4-ss-password-hash.html)
 
  The second mechanism is a normal authentication. Not all the servers support the 2 following mechanisms.
 

diff --git a/source/apacheds/advanced-ug/4.1.1.3-unauthenticated-authn.md b/source/apacheds/advanced-ug/4.1.1.3-unauthenticated-authn.md
index d45c080..3a817bd 100644
--- a/source/apacheds/advanced-ug/4.1.1.3-unauthenticated-authn.md
+++ b/source/apacheds/advanced-ug/4.1.1.3-unauthenticated-authn.md

@@ -4,8 +4,8 @@
 navPrevText: 4.1.1.2 - Name/Password Authentication
 navUp: 4.1.1-simple-authn.html
 navUpText: 4.1.1 - Simple Authentication
-navNext: 4.1.2-sasl-authn.html
-navNextText: 4.1.2 - SASL authentication
+navNext: 4.1.1.4-ss-password-hashs.html
+navNextText: 4.1.1.4 Server side password hashing
 ---
 
 # 4.1.1.3 - Unauthenticated Authentication
@@ -15,5 +15,7 @@
 We won't go any deeper into this 'feature', those interested in the rational behind it and the associated drawbacks can read the following links :
 
   [RFC 4513, Unauthenticated Authentication Mechanism of Simple Bind](https://tools.ietf.org/html/rfc4513#section-5.1.2)
+
 and
+
   [RFC 4513, Unauthenticated Mechanism Security Considerations](https://tools.ietf.org/html/rfc4513#section-6.3.1)

diff --git a/source/apacheds/advanced-ug/4.1.1.4-ss-password-hash.md b/source/apacheds/advanced-ug/4.1.1.4-ss-password-hash.md
index 57d6f0f..1442d7a 100644
--- a/source/apacheds/advanced-ug/4.1.1.4-ss-password-hash.md
+++ b/source/apacheds/advanced-ug/4.1.1.4-ss-password-hash.md

@@ -14,7 +14,7 @@
 
 For this reason, a mechanism has been added that can automatically hash passwords that are added or modified, beside the standard **PasswordModify** extended operation.
 
-Any entry containing the **userPassword** attrribute will automatically sees its value hashed ac cordingly to an algorithm that can be chosend at start time.
+Any entry containing the **userPassword** attribute will automatically sees its values hashed accordingly to an algorithm that can be chosen.
 
 We use a specific interceptor (_passwordHashing_) that needs to be activated to enable this feature. This can be done using _Apache Directory Studio_, by clicking in the _Enable server-side password hashing_ box in the _LDAP/LDAPS Servers_ tab, section _advanced_:
 
@@ -35,7 +35,20 @@
 * SSHA-512
 * PKCS552
 
-Once restarted, any entry containing a **userPassword** attruibute modification or addition will get teh associated value hashed. 
+Once restarted, any entry containing a **userPassword** attruibute modification or addition will get the associated value hashed. 
+
+Another option would be to inject the interceptor configuration in the server configuration, using a **LDIF** file like:
+
+    # turn on Server-side password hash
+    dn: ads-interceptorId=passwordHashingInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config
+    changetype: modify
+    replace: ads-enabled
+    ads-enabled: TRUE
+    -
+    replace: ads-hashalgorithm
+    ads-algorithm: &lt;the selected algorithm&gt;
+    -
+