Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 38.3
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:10
on 2025/09/03 13:10
Change comment:
There is no comment for this version
To version 38.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:09
on 2025/09/03 13:09
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -70,15 +70,12 @@ 70 70 71 71 * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API) 72 72 73 -(% class="box warningmessage" %) 74 -((( 75 75 ⚠ **Note** 76 -Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track. 77 -))) 74 +Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track. 78 78 79 -* When Dependency-Track is added as a tool to an existing or new project, a corresponding pris automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration :76 +* 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 : 80 80 ** Role mapping: ((( 81 -|=Project Role in DevOps Portal|=Permissions in Dependency-Track 78 +|=Project Role in DevOps Portal|=Permissions in Dependency-Track 82 82 |Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 83 83 |Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 84 84 |Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS