Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 51.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 14:08
Change comment: Deleted object
To version 57.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 14:31
Change comment: Update document after refactoring.

Summary

Details

Page properties
Content
... ... @@ -18,8 +18,8 @@
18 18  
19 19  == Preconditions in DevOps portal to access Dependency-Track ==
20 20  
21 -1. A Dependency-Track license must be assigned to the user by a Portal Admin.
22 -1. Deptrack must be added to the tool list of the project by a Project Admin or Portal Admin.
21 +1. A DepTrack license must be assigned to the user by a Portal Admin.
22 +1. DepTrack must be added to the tool list of the project by a Project Admin or Portal Admin.
23 23  
24 24  (% class="box warningmessage" %)
25 25  (((
... ... @@ -27,7 +27,7 @@
27 27  Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency-Track project.
28 28  )))
29 29  
30 -After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
30 +After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service tool chain, can be accessed via the DevOps Portal or directly through the Depdency-Track URL.
31 31  
32 32  == Via DevOps Portal ==
33 33  
... ... @@ -38,9 +38,9 @@
38 38  (% class="box warningmessage" %)
39 39  (((
40 40  ⚠ **Note**
41 -If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again. 
42 -For some reason, you may need to click more than one option in OpenID or trigger the login section ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
43 -\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
41 +If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions. To resolve this issue, please log out and then log in again. 
42 +For some reason, you may need to click more than one time on the OpenID button or go to the login page ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
43 +\\[[image:login1.png||alt="Untitled2.png" data-xwiki-image-style-border="true" height="297" width="650"]]
44 44  )))
45 45  
46 46  == Via Direct URL ==
... ... @@ -48,35 +48,31 @@
48 48  You can also access Dependency-Track directly using the following link format:
49 49  [[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/projects>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance.
50 50  
51 -If you are not already logged in to another tool in the toolchain or the DevOps portal, then you have to login using your configured SSO credentials.
51 +If you are not already logged in to another tool in the tool chain or the DevOps portal, then you have to log in using your configured SSO credentials.
52 52  
53 53  
54 54  = Projects =
55 55  
56 -After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
56 +After creating a DevOps project in the portal, a Dependency-Track project is automatically created. The type of the new project is** Collection Project**. Subprojects which keep the real SBOM scan results are later created as children of this collection project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
57 57  
58 -== Dependency-Track Jenkins Integration ==
58 +For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
59 59  
60 -When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track project. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
60 +== Integration with Jenkins ==
61 61  
62 +The [[Jenkins Shared Library>>url:https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/Jenkins/Jenkins%20Shared%20Library/]] will automatically create SBOM (Software Bill of Materials) files for maven projects and upload them to Dependency-Track.
62 62  
63 -== Collection Project ==
64 +[[image:1756907509490-678.png]]
64 64  
65 -In Dependency-Track, these Maven builds are organized under a **Collection Project**. Subprojects (for example, individual modules of a Maven project) are created as children of the DevOps portal project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
66 -For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
66 +A new Dependency-Track sub project is automatically created on the fly.
67 67  
68 -= Users and Roles =
68 +Currently, this option is only available for Maven projects.
69 69  
70 -* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
71 71  
72 -(% class="box warningmessage" %)
73 -(((
74 -⚠ **Note**
75 -Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
76 -)))
71 += Users and Roles =
77 77  
78 -* When Dependency-Track is added as a tool to an existing or new project, a corresponding Dependency-Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration: 
79 -** Role mapping: (((
73 +* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API).
74 +
75 +* Users assigned to a project in the DevOps Portal are automatically added to the matching Dependency-Track projects with the roles as shown below:(((
80 80  |=Project Role in DevOps Portal|=Permissions in Dependency-Track
81 81  |Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
82 82  |Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
1756907509490-678.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,0 +1,1 @@
1 +5.4 KB
Content
© 2018-2025 T-Systems International GmbH