Changes for page Dependency-Track

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -14,20 +14,20 @@
14	14
15	15	= Accessing Dependency-Track =
16	16
17		-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.
	17	+Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it is only available to pilot customers. To get started, a few prerequisites need to be in place.
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
22		-1. Dependency-Track must be added to the tool list of the project
	21	+1. A Dependency Track license must be assigned to the user
	22	+1. Deptrack must be added to the tool list of the project
23	23
24	24	(% class="box warningmessage" %)
25	25	(((
26	26	⚠ **Note**
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.
	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 toolchain, can be accessed via the DevOps Portal or directly through a URL.
31	31
32	32	== Via DevOps Portal ==
33	33
...	...	@@ -38,13 +38,14 @@
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:
	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.
42	42	\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
43	43	)))
44	44
45	45	== Via Direct URL ==
46	46
47		-You can also access Dependency-Track directly using the following link format:
	48	+You can also access Dependency Track directly using the following link format:
48	48	[[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.
49	49
50	50	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.
...	...	@@ -52,14 +52,16 @@
52	52
53	53	= Projects =
54	54
55		-== Dependency-Track Jenkins Integration ==
	56	+After creating a DevOps project in the portal, a Dependency Track project is automatically created.
56	56
57		-When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
	58	+== Dependency Track Jenkins Integration ==
58	58
	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.
59	59
	62	+
60	60	== Collection Project ==
61	61
62		-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.
	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.
63	63	For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
64	64
65	65	= Users and Roles =
...	...	@@ -69,7 +69,7 @@
69	69	(% class="box warningmessage" %)
70	70	(((
71	71	⚠ **Note**
72		-Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
	75	+Projects in the DevOps portal are mapped to the corresponding teams in Dependency-rack.
73	73	)))
74	74
75	75	* 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 :