DefectDojo
diff --git a/‎.github/workflows/integration-tests.yml
Lines changed: 1 addition & 0 deletions b/‎.github/workflows/integration-tests.yml
Lines changed: 1 addition & 0 deletions
diff --git a/‎docker/entrypoint-integration-tests.sh
Lines changed: 9 additions & 0 deletions b/‎docker/entrypoint-integration-tests.sh
Lines changed: 9 additions & 0 deletions
diff --git a/‎docs/content/en/contributing/how-to-write-a-parser.md
Lines changed: 36 additions & 0 deletions b/‎docs/content/en/contributing/how-to-write-a-parser.md
Lines changed: 36 additions & 0 deletions
@@ -100,6 +100,7 @@ jobs:
           "tests/dedupe_test.py",
           "tests/check_various_pages.py",
           "tests/notifications_test.py",
+          "tests/tool_config.py",
         ]
         profile: ["mysql-rabbitmq", "postgres-redis"]
       fail-fast: false
 
@@ -238,5 +238,14 @@ else
     # else
     #     echo "Error: Zap integration test failed"; exit 1
     # fi
+
+    test="Tool Config integration tests"
+    echo "Running: $test"
+    if python3 tests/tool_config.py ; then
+        success $test
+    else
+        fail $test
+    fi
+
     exec echo "Done Running all configured integration tests."
 fi
@@ -39,6 +39,7 @@ $ docker-compose build --build-arg uid=1000
 |`unittests/scans/<parser_dir>/{many_vulns,no_vuln,one_vuln}.json` | Sample files containing meaningful data for unit tests. The minimal set.
 |`unittests/tools/test_<parser_name>_parser.py` | Unit tests of the parser.
 |`dojo/settings/settings.dist.py`               | If you want to use a modern hashcode based deduplication algorithm
+|`doc/content/en/integrations/parsers`          | Documentation, what kind of file format is required and how it should be obtained 
 
 ## Factory contract
 
@@ -91,6 +92,35 @@ class MyToolParser(object):
 
 ```
 
+## API Parsers
+
+Some reports are not reachable as a file that the user or pipeline can upload but the results of the scans have to be downloaded via API (or we just want to add support for multiple methods).
+In that case, an "API parser" is needed. Core code is the same as a regular parser but there are some additional requirements.
+
+### Which files do you need to modify? (API Parsers only)
+
+| File                                              | Purpose
+|-------                                            |--------
+|`dojo/tools/api_<parser_dir>/api_client.py`        | API client should perform all HTTP API calls and JSON with data from the API
+|`dojo/tools/api_<parser_dir>/importer.py`          | Importer should prepare the API client and process its results
+|`dojo/tools/api_<parser_dir>/parser.py`            | Parser should fetch processed data from the importer
+|`unittests/tools/test_api_<parser_name>_parser.py` | Unit tests of the parser.
+|`unittests/tools/test_api_<parser_name>_importer.py` | Unit tests of the importer.
+|`dojo/tool_config/factory.py`                      | Parser must be listed in `SCAN_APIS`
+|`unittests/test_tool_config.py`                    | Unit tests for content of hints and other metadata
+
+### Factory contract (API Parsers only)
+
+1. Parser directory *MUST* starts with `api_`
+   - ex: `dojo/tools/api_mytool`
+2. class-name of parser *MUST* starts with `Api`
+   - ex: `ApiMytoolParser`
+3. Parser *MUST* implements function `def api_scan_configuration_hint(self)` which returns a string with a hint, on how to configure service keys in Product ...TODO. Using of HTML tag `<b>` is required. Help will be rendered on the website.
+   - ex: `return 'the field <b>Service key 1</b> has to be set to ID of the project. <b>Service key 2</b> has to be set to the version of the project'`
+4. Parser *MUST* implemets function `def requires_tool_type(self, scan_type)` which returns name of the required `Tool_Type`. 
+5. Parser *MUST NOT* create related `Tool_Type`. It will be created automatically based on the function `requires_tool_type`.
+6. API client *SHOULD* implemets `def test_connection(self):` and `def test_product_connection(self, api_scan_configuration):` to be able to test connectivity and test permissions. It should return string with a sucessfull status (like _you have access to 125 projects_) or raise an exception.
+
 ## Template Generator
 
 Use the [template](https://github.com/DefectDojo/cookiecutter-scanner-parser)  parser to quickly generate the files required. To get started you will need to install [cookiecutter](https://github.com/cookiecutter/cookiecutter).
@@ -284,6 +314,12 @@ for finding in findings:
         endpoint.clean()
 ```
 
+### Tests API Parsers
+
+Not only parser but also importer should be tested.
+`patch` method from `unittest.mock` is usualy usefull for simulating API responses.
+It is highly recommeded to use it.
+
 ## Other files that could be involved
 
 ### Change to the model
Original file line number	Diff line number	Diff line change
`@@ -100,6 +100,7 @@ jobs:`
`100`	`100`	`"tests/dedupe_test.py",`
`101`	`101`	`"tests/check_various_pages.py",`
`102`	`102`	`"tests/notifications_test.py",`
	`103`	`+ "tests/tool_config.py",`
`103`	`104`	`]`
`104`	`105`	`profile: ["mysql-rabbitmq", "postgres-redis"]`
`105`	`106`	`fail-fast: false`