Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 23.3
edited by Milad Afshar-Jahanshahi
on 2025/09/03 09:12
Change comment: There is no comment for this version
To version 26.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 09:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,11 +18,26 @@
18 18  
19 19  = Accessing Dependency-Track =
20 20  
21 +(% class="box warningmessage" %)
22 +(((
23 +Pilotkunden Preview ist
24 +)))
25 +
21 21  == Preconditions in DevOps portal to access Dependency-Track ==
22 22  
23 23  1. A Dependency-Track license must be assigned to the user
24 24  1. Dependency-Track must be added to the tool list of the project
25 25  
31 +(% class="box warningmessage" %)
32 +(((
33 +⚠ **Note**
34 +Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat
35 +)))
36 +
37 +
38 +
39 +
40 +
26 26  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.
27 27  
28 28  == Via DevOps Portal ==
... ... @@ -46,6 +46,14 @@
46 46  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.
47 47  
48 48  
64 +
65 +== Dependency-Track Jenkins Interaction ==
66 +
67 +Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
68 +
69 +
70 +== Collection Project und Unterprojekte ==
71 +
49 49  = Users, Projects and Roles =
50 50  
51 51  * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
... ... @@ -56,7 +56,7 @@
56 56  * When Dependency-Track is added as a tool to an existing or new project, a corresponding subwiki is automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration : 
57 57  ** Role mapping: (((
58 58  |=Project Role in DevOps Portal|=Permissions in XWiki
59 -|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
82 +|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
60 60  |Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
61 61  |Developer|(% colspan="1" %)Similar to Master
62 62  |Viewer|Read-only access. Can only view content, no edits or comments allowed
... ... @@ -66,7 +66,7 @@
66 66  
67 67  = Main Features =
68 68  
69 -Inside DevOps-as-a-Service, XWiki is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
92 +Inside DevOps-as-a-Service, deptrack is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
70 70  
71 71  == Collaborative Content Editing ==
72 72  
XWiki.XWikiComments[0]
Comment
... ... @@ -2,9 +2,9 @@
2 2  
3 3  Optionales Tool: aktivieren als Project Admin für das Projekt, zuweisen von Lizenzen als Portal Admin an die entsprechenden User
4 4  
5 -Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat
5 +Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat  ~-~-> Done
6 6  
7 -Dashboard -> DepTrack Login Seite
7 +Dashboard -> DepTrack Login Seite  ~-~-> DOne
8 8  
9 9  Pilotkunden Preview ist
10 10  
© 2018-2025 T-Systems International GmbH