> For the complete documentation index, see [llms.txt](https://docs.mosip.io/compliance-tool-kit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/compliance-tool-kit/how-to-guides/how-to-set-up-ctk/setup-steps-0.0.9.md).

# 0.0.9

## Pre-requisites

CTK should be deployed with the required dockers.

* compliance-toolkit-service: 0.0.9-B1
* compliance-toolkit-ui: 0.0.9-B1

Dependent Service (dockers)

* Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1-B2
* Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
* Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
* Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
* Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
* KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
* Postgres: mosipid/postgres-init: 1.2.0.1-B1
* Config Server: config-server: mosipid/config-server: 1.1.2
* Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
* ClamAV: clamav/clamav: latest
* MinIO

***Note***:

* Ensure that in the `kernel-default.properties`, the value of `mosip-toolkit-client` is set in `auth.server.admin.allowed.audience`. If this was not set by default, then set it and restart `kernel-auth-service` and `compliance-toolkit-service`.
* Check if the roles given to `mosip-pms-client` should match with any of the roles for following config property.

  ```
      mosip.role.keymanager.postverifycertificatetrust=XXX
  ```

  This config property is available in: <https://github.com/mosip/mosip-config/blob/${ENV\\_NAME}/kernel-default.properties>

  *For Example*:

  mosip.role.keymanager.postverifycertificatetrust=`ZONAL_ADMIN`, `GLOBAL_ADMIN`, `PMS_ADMIN`, `PMS_USER`

  Then `mosip-pms-client` should have any of the above roles.

## Steps to setup mosip-compliance-toolkit

1\. Browse to [mosip-compliance-toolkit](https://github.com/mosip/mosip-compliance-toolkit/tree/0.0.9).

2\. The resources folder would contain schemas, test data and test cases that need to be added to MinIO and DB.

![](/files/Xxa2zG8338RgMB7f7hQS)

## Steps to upload resources to MinIO

1\. Log in to MinIO from the browser.

2\. Create a `compliance-toolkit` bucket.

3\. Create a new folder named `testdata` in the above bucket and upload all test data zip files from the resources folder to this folder.

4\. Create a new folder named `schemas` in the above bucket and upload all **sbi** and **sdk** schemas, **testcase** schema from the resources folder to this folder.

*Note*: *There is no need to upload `compliance_test_definitions_sbi.json` and `compliance_test_definitions_sdk.json`.*

5\. Restart the pods after adding new files in MinIO.

## Using Postman

1\. Using Keycloak, create a new user for the compliance toolkit.

2\. Make sure to add the email ID. Also, give the user `GLOBAL_ADMIN`.

3\. Log in to the compliance toolkit in your environment with above the Keycloak user.

4\. Open the developer tools and copy the `Authorization` token from the headers section under the `Networks` tab.

5\. Add the `Authorization` token in postman, copy the token and place it in the headers section of the request (Cookie=Authentication:eyAjksa...) and send the request.

## Steps to upload test cases to the Database

1\. Open postman and create a POST request.

2\. URL endpoint `https://{base_URL}/v1/toolkit/saveTestCases`

3\. Copy the Authorization token in the request header as mentioned in the `Using Postman` section.

4\. Open the resources folder in the project.

5\. `compliance_test_definitions_sbi.json` file has all the test cases in it.

6\. Copy the test cases array from this file and prepare a request as shown below.

7\. Request body for `saveTestCases` request

```
{
    "version": "1.0",
    "requesttime": "2022-10-29T06:06:51.174Z",
    "metadata": null,
    "request": {
        "testCases": [
<Paste the testcases here>
                     ]
               }
}
```

8\. Change the `requesttime` to the current day and send the request.

9\. The same should be done for `compliance_test_definitions_sdk.json`.