Changes for page Dependency-Track
Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 36.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:04
on 2025/09/03 13:04
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
-
... ... @@ -16,8 +16,6 @@ 16 16 17 17 [[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]] 18 18 19 -[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]] 20 - 21 21 = Accessing Dependency-Track = 22 22 23 23 Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it’s only offered in the Pilotkunden Preview. To get started, a few prerequisites need to be in place. ... ... @@ -65,7 +65,7 @@ 65 65 66 66 == Collection Project == 67 67 68 -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 collection. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.66 +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. 69 69 For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation. 70 70 71 71 = Users and Roles = ... ... @@ -77,11 +77,11 @@ 77 77 78 78 * 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 : 79 79 ** Role mapping: ((( 80 -|=Project Role in DevOps Portal|=Permissions in XWiki81 -|Admin| ''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'82 -|Master|(% colspan="1" %)C anview,comment,and edit pages,butcannot delete content83 -|Developer|(% colspan="1" %)S imilartoMaster84 -|Viewer| Read-only access.Canonly view content,no edits or comments allowed78 +|=Project Role in DevOps Portal|=Permissions in Dependency-Track 79 +|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 80 +|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 81 +|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS 82 +|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY 85 85 86 86 A detailed description of the XWiki role model can be found [[here>>https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Access%20Rights/Permission%20types/]] 87 87 )))