svn commit: r1689336 - in /directory/site/trunk/content/kerby: overview.mdtext quick-start.mdtext

[pl...@apache.org]

Author: plusplusjiajia
Date: Mon Jul  6 08:38:30 2015
New Revision: 1689336

URL: http://svn.apache.org/r1689336
Log:
Change the format.

Modified:
    directory/site/trunk/content/kerby/overview.mdtext
    directory/site/trunk/content/kerby/quick-start.mdtext

Modified: directory/site/trunk/content/kerby/overview.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/kerby/overview.mdtext?rev=1689336&r1=1689335&r2=1689336&view=diff
==============================================================================
--- directory/site/trunk/content/kerby/overview.mdtext (original)
+++ directory/site/trunk/content/kerby/overview.mdtext Mon Jul  6 08:38:30 2015
@@ -20,13 +20,13 @@ Notice: Licensed to the Apache Software
 
 ## The Initiatives/Goals
 
-*Aims as a Java Kerberos binding, with rich and integrated facilities that integrate Kerberos, PKI and token (OAuth2) for both client and server sides.
-*Provides client APIs at the Kerberos protocol level to interact with a KDC server through AS and TGS exchanges.
-*Provides a standalone KDC server that supports various identity back ends including memory based, Json file based, LDAP backed and even Zookeeper backed.
-*Provides an embedded KDC server that applications can easily integrate into products, unit tests or integration tests.
-*Supports FAST/Preauthentication framework to allow popular and useful authentication mechanisms.
-*Supports PKINIT mechanism to allow clients to request tickets using x509 certificate credentials.
-*Supports Token Preauth mechanism to allow clients to request tickets using JWT tokens.
-*Supports OTP mechanism to allow clients to request tickets using One Time Password.
-*Provides support for JAAS, GSSAPI and SASL frameworks that applications can leverage.
-*Minimal dependencies, the core part is ensured to depend only on JRE and SLF4J, for easy use and maintenance.
+* Aims as a Java Kerberos binding, with rich and integrated facilities that integrate Kerberos, PKI and token (OAuth2) for both client and server sides.
+* Provides client APIs at the Kerberos protocol level to interact with a KDC server through AS and TGS exchanges.
+* Provides a standalone KDC server that supports various identity back ends including memory based, Json file based, LDAP backed and even Zookeeper backed.
+* Provides an embedded KDC server that applications can easily integrate into products, unit tests or integration tests.
+* Supports FAST/Preauthentication framework to allow popular and useful authentication mechanisms.
+* Supports PKINIT mechanism to allow clients to request tickets using x509 certificate credentials.
+* Supports Token Preauth mechanism to allow clients to request tickets using JWT tokens.
+* Supports OTP mechanism to allow clients to request tickets using One Time Password.
+* Provides support for JAAS, GSSAPI and SASL frameworks that applications can leverage.
+* Minimal dependencies, the core part is ensured to depend only on JRE and SLF4J, for easy use and maintenance.

Modified: directory/site/trunk/content/kerby/quick-start.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/kerby/quick-start.mdtext?rev=1689336&r1=1689335&r2=1689336&view=diff
==============================================================================
--- directory/site/trunk/content/kerby/quick-start.mdtext (original)
+++ directory/site/trunk/content/kerby/quick-start.mdtext Mon Jul  6 08:38:30 2015
@@ -27,50 +27,46 @@ The distribution of Kerby.
 ### To run with a standalone kdc server, kinit and kadmin
 
 * Generate libraries for distribution:
-```
-mvn package -Pdist
-```
+
+    mvn package -Pdist
 
 * Run kadmin to add principals:
-```
-sh kerby-dist/tool-dist/bin/kadmin.sh [server-conf-dir]
-```
+
+    sh kerby-dist/tool-dist/bin/kadmin.sh [server-conf-dir]
 
   In kadmin, you can type "?" for help. For now, the kadmin only supports to add principals to json-backend. (Working in progress).
 
 * Start kerby-kdc-server:
-```
-sh kerby-dist/kdc-dist/bin/start-kdc.sh –start [server-conf-dir] [work-dir]
-```
+
+    sh kerby-dist/kdc-dist/bin/start-kdc.sh –start [server-conf-dir] [work-dir]
 
 * Run kinit:
-```
-sh kerby-dist/tool-dist/bin/kinit.sh [principal-name]
-```
+
+    sh kerby-dist/tool-dist/bin/kinit.sh [principal-name]
 
   If you don't specify [server-conf-dir] in step 2 or 3, it will be set as /etc/kerby. In [server-conf-dir], there should be kdc.conf, backend.conf. And in /etc/, there should be krb5.conf.
 
 An example of kdc.conf:
-```
-[kdcdefaults]
-    kdc_host = localhost
-    kdc_tcp_port = 8015
-    kdc_realm = TEST.COM
-```
+
+    [kdcdefaults]
+        kdc_host = localhost
+        kdc_tcp_port = 8015
+        kdc_realm = TEST.COM
+
 An example of json backend backend.conf:
-```
-kdc_identity_backend = org.apache.kerby.kerberos.kdc.identitybackend.JsonIdentityBackend
-backend.json.file = /tmp/kerby/jsonbackend
-```
+
+    kdc_identity_backend = org.apache.kerby.kerberos.kdc.identitybackend.JsonIdentityBackend
+    backend.json.file = /tmp/kerby/jsonbackend
+
 An example of zookeeper backend backend.conf:
-```
-kdc_identity_backend = org.apache.kerby.kerberos.kdc.identitybackend.ZookeeperIdentityBackend
-data_dir = /tmp/kerby/zookeeper/data
-data_log_dir = /tmp/kerby/zookeeper/datalog
-```
+
+    kdc_identity_backend = org.apache.kerby.kerberos.kdc.identitybackend.ZookeeperIdentityBackend
+    data_dir = /tmp/kerby/zookeeper/data
+    data_log_dir = /tmp/kerby/zookeeper/datalog
+
 An example of krb5.conf:
-```
-[libdefaults]
-    kdc_realm=TEST.COM
-```
+
+    [libdefaults]
+        kdc_realm=TEST.COM
+