xcfit 0.2.0

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/ControllingFitNesseFromTheCommandLine/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/LogFiles/content.txt

@@ -0,0 +1,29 @@
+FitNesse has two different types of logging: system logging and access logging.
+
+!2 System logging
+System logging is performed via ''java.util.logging''. This is the default logging facility bundled with Java. By default only messages with info level and up are logged. The -v option can enable more verbose logging by default. Logging is sent to stderr.
+
+It's possible to fully customize the logging output, including redirecting it to files. In order to do so, one has to create a log configuration file in accordance to the properties available to the different handlers. See the API documentation for [[!-LogManager-!][http://docs.oracle.com/javase/7/docs/api/index.html?java/util/logging/LogManager.html]], [[!-ConsoleHandler-!][http://docs.oracle.com/javase/7/docs/api/index.html?java/util/logging/ConsoleHandler.html]] and [[!-FileHandler-!][http://docs.oracle.com/javase/7/docs/api/index.html?java/util/logging/FileHandler.html]] for some inspiration. FitNesse by default uses a custom log formatter: ''!-<i>fitnesse.logging.LogFormatter</i>-!''. This formatter provides some simple formatting and does only print log severity and exception stack traces for warning level and up.
+
+The default log configuration looks like this:
+
+{{{handlers = java.util.logging.ConsoleHandler
+java.util.logging.ConsoleHandler.formatter = fitnesse.logging.LogFormatter}}}
+!2 Access file
+
+If File logging is turned on (with the -l command line argument) then FitNesse will record all accesses in log files.
+
+A new log file is created every day.
+
+Log files are named fitnesseyyyymmddhhmmss.log, where yyyymmddhhmmss is the time of the first log entry in the file.
+
+Each line in the log file records a separate access.  They are written in standard (common) web log format.  They look like this:{{{
+65.194.52.68 - - [06/Mar/2003:16:33:48 -0600] "GET /FitNesse.UserGuide HTTP/1.1" 200 1965
+65.194.52.68 - - [06/Mar/2003:16:33:49 -0600] "GET /files/images/FitNesseLogoIcon.jpg HTTP/1.1" 200 15026
+65.194.52.68 - - [06/Mar/2003:16:33:54 -0600] "GET /files HTTP/1.1" 404 380
+65.194.52.68 - - [06/Mar/2003:16:34:00 -0600] "GET /files/ HTTP/1.1" 200 650
+65.194.52.68 - - [06/Mar/2003:16:34:00 -0600] "GET /files/images/FitNesseLogoIcon.jpg HTTP/1.1" 200 15026
+65.194.52.68 - - [06/Mar/2003:16:34:04 -0600] "GET /files/logs/ HTTP/1.1" 200 414
+65.194.52.68 - - [06/Mar/2003:16:34:04 -0600] "GET /files/images/FitNesseLogoIcon.jpg HTTP/1.1" 200 15026
+65.194.52.68 - - [06/Mar/2003:16:34:05 -0600] "GET /files/logs/fitnesse20030306163348.log HTTP/1.1" 200 650
+}}}

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/LogFiles/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/NetworkSecurity/content.txt

@@ -0,0 +1,234 @@
+!2 Protect your servers and your data!
+To protect the integrity of your environment it is strongly recommended to encrypt and authenticate the network traffic
+between the different FitNesse processes. Both will be achieved with SSL. 
+Without this 
+ * passwords will be send unencrypted over the network 
+ * your system under test would accept commands from any server which can access it over the network. 
+ * this is especially an issue if the system under test runs in demon mode. 
+
+In addition to this also enable user authentication with a PasswordCipher .
+ 
+!4 '''Only with self created certificates you achieve security!'''
+SSL requires ''certificates'' which identify uniquely each server.
+It just takes 1 minutes to create your own certificates, please take the time to do this.
+The certificates in the fitnesse distribution are just there for running junit tests. Never use them for your fitnesse instance. 
+
+!2 1. Creating your private SSL keys and certificates
+The below just gives the commands how you can create certificates and how to sign them yourself to get started. 
+In a professional environment your company might have further guidelines. Please contact your network or security administrator.
+If you are new to SSL browse the web to understand how it works.
+
+A minimum SSL configuration consists of 
+| |                                                                                               |value used in sample commands        |Must be changed by you|
+|1|A keystore file per server with the private key of each of your server which has been certified|'''fitnesse.jks'''                   |No                    |
+|2|A password for this keystore file                                                              |'''!-PutYourKeyStorePasswordHere-!'''|Yes                   |
+|3|A truststore file which defines with whom your servers should be allowed to communicate        |'''fittrust.jks'''                   |No                    |
+|4|A password for this truststore file                                                            |'''!-PutYourTrustPasswordHere-!'''   |Yes                   |
+
+The first three must be known by FitNesse at runtime. To do this you expand the class '''fitnesse.socketservice.SslParameters'''
+The last one is only required when you want to modify the truststore. For running FitNesse it is not required.
+
+The tool '''keytool''' is used to generate the keys. It is part of the jdk.
+
+Below are sample commands to get started. You might add or change values according to your setup.
+
+!* 1.1 Switch to the directory from which you start fitnesse 
+cd .. 
+*!
+
+!* 1.2 Create your server keys and certificate 
+keytool -genkey -keyalg RSA -alias selfsigned -keystore '''fitnesse.jks''' -storepass '''!-PutYourKeyStorePasswordHere-!''' -validity 400
+*!
+You will be asked for further input. 
+When asked for your first and last name enter your server name with the domain instead like ''www.fitnesse.org''.
+The remaining items don't matter.
+When asked for the ''key password'' just press enter.
+After this step a new file '''fitnesse.jks''' is in your current folder
+
+!* 1.3  Protect the '''fitnesse.jks''' with all measures your operating system supports
+chmod ...
+*!
+'''IMPORTANT''': Give only read access to users who need this!
+Remove read and write access for anybody else.
+
+!3 1.4 Tell FitNesse your password and the name and location of the keystore file
+
+Create the following class and add it to the classpath of FitNesse
+!* custom SSL Parameter class
+package '''your.package'''
+import fitnesse.socketservice.SslParameters;
+
+public class '''!-YourServerSslParameters-!''' extends !-SslParameters-! {
+  public '''!-YourServerSslParameters-!'''(){
+	super();
+	// Below is only for demonstration purpose 
+	// Don't hard code passwords in clear text
+	// A) Ask the user to enter it each time the system starts. That's the most secure way but often not convenient.
+	// B) Read it from a file where it is stored obfuscated.
+	String password = "'''!-PutYourKeyStorePasswordHere-!'''";
+	setKeyStorePassword(password);
+	setKeyStoreFilename("'''fitnesse.jks'''");
+	setTrustStoreFilename("'''fitnesse.jks'''");
+  }
+}
+*!
+
+You can use the same class also for '''!-YourSutSslParameters-!''' in the following steps.
+
+
+!2 2. Secure Communication between the browser and the Wiki Server
+Instead of http the communication will be https
+
+!3 2.1 Add the following to plugins.properties
+
+!*  plugins.properties
+!-##-!
+!-#  Wiki Server uses https-!
+wiki.protocol=https
+wiki.protocol.ssl.parameter.class='''your.package.YourServerSslParameters'''
+*!
+
+!3 2.2 In your browser
+Enter '''https://localhost:port''' in your webbrowser to connect to the wiki server
+
+If you signed the ''certificates'' yourself your browser will give a security warning. 
+Accept this warning after you checked the certificate. Add a permanent exception for this certificate to your browser 
+to avoid that you get this warning each time in the future.
+
+!3 2.3 Client Authentication
+If users have certificates, client authentication may be required.  To enable client authentication set the following plugins.properties:
+
+!*  plugins.properties
+!-##-!
+!-#  Wiki Server uses https-!
+wiki.protocol=https
+wiki.protocol.ssl.parameter.class='''your.package.YourServerSslParameters'''
+wiki.protocol.ssl.client.auth='''required'''
+*!
+
+Authorization can be accomplished with client certificates with the creation of a custom Authenticator.  The Authenticator has access to the peer dn from the Request.  Access can be granted or denied based on the dn.
+
+!2 3. Secure Communication between  the Test System and the System Under Test
+
+This is currently only supported for the SLIM java client.
+FIT and SLIM clients for other programming languages must still be enhanced.
+
+!3 3.1. Configuring SSL on the Test System
+The FitNesse Test System and the FitNesse Wiki server are a single process and share the same SSL configuration
+If you have not enabled https for the wiki you have to add the below to configure SSL for the test system.
+
+!*  plugins.properties
+wiki.protocol.ssl.parameter.class='''your.package.YourServerSslParameters'''
+*!
+
+!3 3.2. Configuring SSL on the SUT
+Either enable this for individual test pages by defining the variable
+!* SLIM_SSL
+ !define SLIM_SSL ('''your.package.YourSutSslParameters''') 
+*!
+
+or enable this for all SLIM Test Systems on all pages by adding below to 'plugins.properties'.
+This configuration takes precedents above an individual page configuration.
+
+!*  plugins.properties
+!-##-!
+!-#  Enable SSL on the Test Systems -!
+slim.ssl='''your.package.YourSutSslParameters'''
+*!
+
+If you use remote debugging and started the SUT manually add the following additional parameter to the command line
+!* SSL command line parameter
+-ssl '''your.package.YourSutSslParameters'''
+*!
+
+
+
+!2 4. Troubleshooting SSL configuration
+
+!3 4.1. Start FitNesse with the following two extra parameters to get more output to identify any issues
+ * -v
+ * -Djavax.net.debug=ssl,keymanager
+
+!* Example
+java ''-Djavax.net.debug=ssl,keymanager'' -cp fitnesse-standalone.jar fitnesseMain.FitNesseMain ''-v''
+*!
+!3 4.2. Define the following on your test page to get more output from the SUT
+!* variables on test pages
+!- !define-! SLIM_FLAGS (-v)
+!- !define-! COMMAND_PATTERN  (java ''-Djavax.net.debug=ssl,keymanager'' -cp %p %m)
+*! 
+
+!3 4.3. Define the following properties to speed up troubleshooting
+This reduces the number of connection attempts. A test with a faulty configuration is then aborted quicker.
+!*  plugins.properties
+slim.timeout=1
+slim.pool.size=1
+*! 
+
+
+!3 4.4. Typical error messages in the output from the SUT
+!* Error while executing SLIM instructions: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
+Test System is not trusting the SUT - Add the certificate from the SUZ to the truststore on the server
+*!
+
+!* Error while executing SLIM instructions: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: null cert chain
+SUT is not trustig the Test System - Add the certificate from the server to the truststore on the SUT
+*!
+
+!* java.security.NoSuchAlgorithmException: Error constructing implementation ... java.io.IOException: Keystore was tampered with, or password was incorrect
+Check the password you provided for the keystore
+*!
+
+!2 5. Configuring SSL for a multi server environment 
+If your system under test doesn't runs on the same server as your Wiki Server consider the blow setup.
+
+!* 1.1 Command to create your server keys and certificate 
+keytool -genkey -keyalg RSA -alias selfsigned -keystore '''fitnesse.jks''' -storepass '''!-PutYourKeyStorePasswordHere-!''' -validity 400
+keytool -export -alias selfsigned -file fitnesse.cer -keystore '''fitnesse.jks''' -storepass '''!-PutYourKeyStorePasswordHere-!'''
+*!
+You will be asked for further input. 
+When asked for your first and last name enter your server name with the domain instead like ''www.fitnesse.org''.
+The remaining items don't matter.
+When asked for the ''key password'' just press enter.
+
+If you have more then one server on which you run SUT you should do this for each server.
+To not overwrite the keystores and certificates change each time the '''fitnesse.jks''' and '''fitnesse.cer''' parameters.
+
+'''IMPORTANT''': Protect the '''fitnesse.jks''' with all measures your operating system supports! Give only read access to users who need this. 
+Remove read and write access for anybody else.
+
+
+!* 1.2 Commands to create your trust store 
+keytool -import -v -trustcacerts -alias '''!-uniqueSUTName-!''' -storepass '''!-PutYourTrustPasswordHere-!''' -file fitnesse.cer -keystore '''fittrust.jks'''
+*!
+If you have created more than one set of files repeat this command for each '''*.cer''' file but put all in the 
+same truststore file '''fittrust.jks''' 
+
+
+!3 1.3 Configure FitNesse with your certificates
+Once you have run these commands you have two types of files in your current directory '''fitnesse.jks''' and '''fittrust.jks'''
+Copy both into your FitNesse directoy from which you start FitNesse or your SUT. Make again sure that your '''fitnesse.jks''' 
+and '''fittrust.jks''' are protected.
+
+Create the following class and add it to the classpath of FitNesse
+!* custom SSL Parameter class
+package '''your.package'''
+import fitnesse.socketservice.SslParameters;
+
+public class '''!-YourServerSslParameters-!''' extends !-SslParameters-! {
+  public '''!-YourServerSslParameters-!'''(){
+	super();
+	// Below is only for demonstration purpose 
+	// Don't hard code passwords in clear text
+	// A) Ask the user to enter it each time the system starts. That's the most secure way but often not convenient.
+	// B) Read it from a file where it is stored obfuscated.
+	String password = "'''!-PutYourKeyStorePasswordHere-!'''";
+	setKeyStorePassword(password);
+	setKeyStoreFilename("'''fitnesse.jks'''");
+	setTrustStoreFilename("'''fittrust.jks'''");
+  }
+}
+*!
+
+Create identical classes named '''!-YourSutSslParameters-!''' for each server running SUT but give the values of the 
+'''fitnesse.jks''' you created for each server and add the class to the classpath of the SUT.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/NetworkSecurity/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<Help>HowTo setup https, SSL and security on the network</Help>
+<LastModifyingUser>six42</LastModifyingUser>
+<RecentChanges/>
+<Search/>
+<Static/>
+<Suites>SSL, security, administration, https</Suites>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/PasswordCipher/content.txt

@@ -0,0 +1,9 @@
+A class used to encrypt password that will be written to a PasswordFile.  Here is the interface.
+{{{
+package fitnesse.authentication;
+
+public interface PasswordCipher
+{
+	public String encrypt(String password) throws Exception;
+}
+}}}

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/PasswordCipher/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<LastModified>20090228113824</LastModified>
+	<RecentChanges>true</RecentChanges>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/PasswordFile/content.txt

@@ -0,0 +1,25 @@
+When starting FitNesse you may specify a PasswordFile by using the ''-a'' command line argument.  A PasswordFile consists of one username and password per line in the form of '''username:password'''.
+
+!3 Human Readable Passwords
+This simple way to create a password file is to list each username:password pair as plain text in the PasswordFile.  However this is not very secure in that anyone who is able to read the PasswordFile will have access to everyones password.  Here's an example:
+{{{Leonardo:katana
+Donatello:bo
+Rafael:sai
+Michaelangelo:nunchaku}}}
+4 users are defined here.  Leonardo whose password is Katana, Donatello whose password is bo, Rafael whose password is sai, and Michaelangelo whose password is nunchaka.
+
+!3 Hashed Passwords
+A password hashing program, similar to unix's '''passwd''' command, is provided with FitNesse. The Password program has the follwoing usage:
+{{{Usage: java fitnesse.authentication.Password [-f <password file>] [-c <password cipher>] <user>
+        -f <password file> {passwords.txt}
+        -c <password cipher> {fitnesse.authentication.HashingCipher} }}}
+By using the Password program with default setting and using the same usernames and passwords as above, the file ''passwords.txt'' will be generated with the following content:
+{{{!fitnesse.authentication.HashingCipher
+Leonardo:VEN4CfBvGCSafZDZNIKh
+Donatello:VvkqQdgBBfCCZHzBUo6J
+Michaelangelo:VBZ1TiB7HMptQsz3d3do
+Rafael:YHVFNHr1fHaIGkLHMTSP}}}
+You can see that the passwords have been hashed and are not humanly readable.  You may also notice a new line.
+!-!fitnesse.authentication.HashingCipher-!
+This should be left as is in the file.  It tells the program with PasswordCipher to use when hashing the passwords.  You may create your own PasswordCipher by implementing the ''!-fitnesse.authentication.PasswordCipher-!'' interface and use it for creating password files using the -c command line argument.
+  

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/PasswordFile/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20081020135111</LastModified>
+  <RecentChanges/>
+  <WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/RestfulServices/JsonProperties/content.txt

@@ -0,0 +1,17 @@
+{{{
+{
+ "Edit": true,
+ "Properties": true,
+ "Prune": false,
+ "RecentChanges": true,
+ "Refactor": true,
+ "Search": true,
+ "Suite": false,
+ "Test": false,
+ "Versions": true,
+ "WhereUsed": true,
+ "secure-read": false,
+ "secure-test": false,
+ "secure-write": false
+}
+}}}

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/RestfulServices/JsonProperties/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit>true</Edit>
+	<Files>true</Files>
+	<Properties>true</Properties>
+	<RecentChanges>true</RecentChanges>
+	<Refactor>true</Refactor>
+	<Search>true</Search>
+	<Versions>true</Versions>
+	<WhereUsed>true</WhereUsed>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/RestfulServices/PageHistoryXml/content.txt

@@ -0,0 +1,19 @@
+{{{
+<PageHistory>
+  <Page>
+    <Name>
+      FitNesse.SuiteAcceptanceTests.SuiteResponderTests.SuiteMoveResponder.TestSimpleMove
+    </Name>
+    <TestResult>
+      <Date>Tue Jul 07 11:08:34 CDT 2009</Date>
+      <ResultLink>
+        FitNesse.SuiteAcceptanceTests.SuiteResponderTests.SuiteMoveResponder.TestSimpleMove?pageHistory&resultDate=20090707110834&format=xml
+      </ResultLink>
+      <Pass>6</Pass>
+      <Fail>0</Fail>
+    </TestResult>
+    ...
+  </Page>
+  ...
+</PageHistory>
+}}}

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/RestfulServices/PageHistoryXml/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit>true</Edit>
+	<Files>true</Files>
+	<Properties>true</Properties>
+	<RecentChanges>true</RecentChanges>
+	<Refactor>true</Refactor>
+	<Search>true</Search>
+	<Versions>true</Versions>
+	<WhereUsed>true</WhereUsed>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/RestfulServices/RestfulPackets/content.txt

@@ -0,0 +1,33 @@
+If you access a page with the ?packet responder as in !style_code(http://myFitNesseHost/MyPage?packet) you will get back a JSON packet that represents the tables on that page.  Only the tables will be part of the packet, any other text is ignored.  The JSON packet begins with an array named !style_code(tables).  Each element of that array corresponds to a table on the page.  The tables use an indentation style to represent the packets.  For example:
+
+!|Customer|
+||name|Bob Someone|
+||id|8402|
+||addr|
+|||Street|555 Witherspoon st.|
+|||city|Anyville|
+|||state|IL|
+|||zip|60083|
+||phone|555-1212|
+
+If you get the packet for this page by accessing http://localhost:${FITNESSE_PORT}/FitNesse.UserGuide.RestfulPackets?packet you will get the following JSON packet:
+{{{
+{"tables": [
+ {"Customer":
+  { "addr":
+   { "Street": "555 Witherspoon st.",
+     "city": "Anyville",
+     "state": "IL",
+     "zip": "60083"
+   },
+    "id": "8402",
+    "name": "Bob Someone",
+    "phone": "555-1212"
+  }
+ }
+]}
+}}}
+
+!3 JSONP
+If you'd like to use ''JSONP'' to fetch the packets. (Or any kind of script injection tecnique).  You can get fitnesse to return the appropriate format by adding !style_code(&jsonp=some_function) on the end of the url.  This will wrap the JSON packet in a function call that looks like this !style_code[some_function({...})]  So, for example, try this link: !style_code(http://localhost:${FITNESSE_PORT}/FitNesse.UserGuide.RestfulPackets?packet&jsonp=load_me).
+