|
| 1 | +--- |
| 2 | +title: "Dependency track integration" |
| 3 | +description: "EMBA now with Dependency track integration" |
| 4 | +date: 2025-11-26T09:01:00+01:00 |
| 5 | +authors: |
| 6 | + - Michael Messner |
| 7 | +draft: false |
| 8 | +tags: |
| 9 | + - EMBA |
| 10 | +--- |
| 11 | + |
| 12 | +EMBA is now able to automatically upload the generated SBOM to your dependency track instance. |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | +To be able to use the dependency track API a API key and special permissions are needed. The following screenshot shows how to create a new Team with an API key and the needed permissions: |
| 17 | + |
| 18 | + |
| 19 | + |
| 20 | +EMBA needs the following dependency track permissions: |
| 21 | +* BOM_UPLOAD |
| 22 | +* PROJECT_CREATION_UPLOAD |
| 23 | +* VIEW_PORTFOLIO |
| 24 | + |
| 25 | +You can find further details about the API within the dependency track documentation here. |
| 26 | + |
| 27 | +Afterwards it should be possible to upload an SBOM via the API: |
| 28 | + |
| 29 | +``` |
| 30 | +curl -X "POST" "http://<DEPENDENCY_TRACK_HOST_IP>/api/v1/bom" \ |
| 31 | + -H 'Content-Type: multipart/form-data' \ |
| 32 | + -H "X-Api-Key: <DEPENDENCY_TRACK_API_KEY>" \ |
| 33 | + -F "autoCreate=true" \ |
| 34 | + -F "projectName=testproject" \ |
| 35 | + -F "bom=@/Path/to/your/CycloneDX-SBOM.json" |
| 36 | +``` |
| 37 | + |
| 38 | +The next step is to build a configuration file for EMBA. As there is a template file available, the easiest way is to copy this file and edit it afterwards: |
| 39 | + |
| 40 | +``` |
| 41 | +cp config/dependencytrack.env.template config/dependencytrack.env |
| 42 | +``` |
| 43 | + |
| 44 | +In the new env file you need to adjust the following parameters: |
| 45 | + |
| 46 | +``` |
| 47 | +DEPENDENCY_TRACK_HOST_IP="<insert your IP address>:8081" |
| 48 | +DEPENDENCY_TRACK_API_KEY="<insert your API key>" |
| 49 | +``` |
| 50 | + |
| 51 | +Afterwards EMBA should be able to upload the generated SBOM to you dependency track instance. |
| 52 | + |
| 53 | +To monitor the upload process it is needed to check the log file for the Q20 module or check the logs of the quest docker container: |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | + |
0 commit comments