Updated the documentation with description for providing "benchAccess…

…Token"

README.md

@@ -38,6 +38,7 @@ Configuration located in file `<cybench-home>/conf/cybench-launcher.properties`
 | **runThreadCount**| Number of threads for benchmark test execution. |  1 |
 | **benchmarkMetadata**| A property which adds extra properties to the benchmarks report such as category or version or context. Configuration pattern is `<fully qualified benchmark class name>=<key1>:<value1>;<key2>:<value2>`. Example which adds category for class CollectionsBenchmarks: `com.gocypher.benchmarks.client.CollectionsBenchmarks=category:Collections;`   |   -  |
 | **userProperties**| User defined properties which will be added to benchmarks report section `environmentSettings->userDefinedProperties` as key/value strings. Configuration pattern:`<key1>:<value1>;<key2>:<value2>`. Example which adds a project name:`user.propname1=My Test Project;` |  -  |
+| **benchAccessToken** | By providing the "bench" token that you get after creating a workspace in CyBench UI, you can send reports to your private directory, which will be visible only to the users that you authorize. | - |
 
 ## Running User-defined Benchmarks using CyBench
 

gocypher-cybench-client/gocypher-cybench-runner/src/main/java/com/gocypher/cybench/launcher/report/ReportingService.java

@@ -196,9 +196,6 @@ public Map<String, String> prepareBenchmarkProperties(String className,
 			}
 			return benchmarkProperties;
 		} catch (Exception e) {
-			benchmarkProperties.put("benchCategory", "CUSTOM");
-			benchmarkProperties.put("benchContext", "Custom");
-			benchmarkProperties.put("benchVersion", "1.0.0");
 			LOG.error("Error on resolving benchmarks category, context and version: class={}", className, e);
 		}
 		return benchmarkProperties;