Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 26.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 09:16
on 2025/09/03 09:16
Change comment:
There is no comment for this version
To version 23.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 08:51
on 2025/09/03 08:51
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,15 +23,6 @@ 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 26 -(% class="box warningmessage" %) 27 -((( 28 -⚠ **Note** 29 -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 30 -))) 31 - 32 - 33 - 34 - 35 35 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. 36 36 37 37 == Via DevOps Portal == ... ... @@ -54,13 +54,10 @@ 54 54 55 55 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. 56 56 48 +⚠ **Note** 49 +Access to the main wiki at [[https:~~/~~/<customer~>.devops.t-systems.net/xwiki>>https://<customer>.devops.t-systems.net/xwiki]] is forbidden due to security restrictions and therefore this page cannot be viewed. 50 + 57 57 58 - 59 -== Dependency-Track Jenkins Interaction == 60 - 61 -Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch 62 - 63 - 64 64 = Users, Projects and Roles = 65 65 66 66 * 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,7 +71,7 @@ 71 71 * 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 : 72 72 ** Role mapping: ((( 73 73 |=Project Role in DevOps Portal|=Permissions in XWiki 74 -|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'62 +|Admin|View, comment, edit, and delete pages 75 75 |Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content 76 76 |Developer|(% colspan="1" %)Similar to Master 77 77 |Viewer|Read-only access. Can only view content, no edits or comments allowed ... ... @@ -81,7 +81,7 @@ 81 81 82 82 = Main Features = 83 83 84 -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.72 +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. 85 85 86 86 == Collaborative Content Editing == 87 87
- 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 ~-~-> Done5 +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 6 6 7 -Dashboard -> DepTrack Login Seite ~-~-> DOne7 +Dashboard -> DepTrack Login Seite 8 8 9 9 Pilotkunden Preview ist 10 10