Wiki source code of DevOps Portal for Admins
Version 1.1 by DevOps-as-a-Service Operator on 2025/02/05 11:33
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | The DevOps portal is used to manage DevOps-as-a-Service, which is a set of tools that aid in the delivery, development, and management of applications throughout the systems development life cycle, as coordinated by an organization that uses DevOps practices. | ||
2 | |||
3 | (% style="color:#003366" %)__Table of contents:__ | ||
4 | |||
5 | {{toc/}} | ||
6 | |||
7 | = Creating user accounts = | ||
8 | |||
9 | After a successful login you can continue with onboarding your colleges. In the top menu, click **Users**, then click **Create User** button: | ||
10 | |||
11 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image2019-6-18_13-47-44.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="138" width="800"]] | ||
12 | |||
13 | Please fill in the required fields with the user's Name and Email address (where the activation email will be sent), and select the Organization (or use the default). | ||
14 | |||
15 | The Organization can be the default organization, or you can create a different organization. Find more information in the [[Creating organizations>>||anchor="HCreatingOrganizations"]] and [[Modify Organizations>>||anchor="HModifyOrganizations"]] sections. | ||
16 | |||
17 | The Portal Role (in this example, it will be USER) can be either Admin (with permission to manage the portal) or User (without permission to change users, organizations, etc.). By default, all user accounts are created as User. | ||
18 | |||
19 | The Tools section lets you choose which tool(s) the user should have access to. | ||
20 | |||
21 | Click **Save** to send the invitation email to the user. Please refer to [[DevOps Portal for Users>>doc:DevOps Portal for Users.WebHome]] for further information regarding the activation process and password change. | ||
22 | |||
23 | [[image:attach:image-2023-4-25_15-48-16.png||data-xwiki-image-style-border="true" height="400"]] | ||
24 | |||
25 | The new user's status will be **LOCKED **until the profile has been activated. Activation can either be done by the user her-/himself (by following the received link) or by an admin user via **More ... → Activate**. The latter option will prompt the admin to manually set the user's password | ||
26 | |||
27 | (% class="box warningmessage" %) | ||
28 | ((( | ||
29 | ⚠ **Note** | ||
30 | Manual activation is not recommended since it bypasses email verification so use with caution! | ||
31 | ))) | ||
32 | |||
33 | [[image:attach:image-2023-5-11_12-38-10.png||data-xwiki-image-style-border="true" thumbnail="true" height="250"]] | ||
34 | |||
35 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:02.jpg||data-xwiki-image-style-border="true" width="894"]] | ||
36 | |||
37 | |||
38 | If needed, a user can be invited again by selecting the **Reinvite** option. This can be used if the user missed the activation deadline mentioned in the email, without locking the user's account. | ||
39 | |||
40 | //[[image:attach:image-2023-4-25_16-28-24.png||thumbnail="true" height="250"]]// | ||
41 | |||
42 | After receiving the email, the user's status will be CREATED. Once the activation is successful, the status will change to ACTIVE. | ||
43 | |||
44 | If an email address was entered incorrectly, the user will need to be deleted and recreated. Email addresses cannot be changed for existing users. | ||
45 | |||
46 | |||
47 | = Modifying user accounts = | ||
48 | |||
49 | A user account can be modified by clicking his / her last name. However, **it's not possible to change a user's e-mail address**. | ||
50 | |||
51 | **[[image:attach:image-2023-4-25_16-26-48.png||data-xwiki-image-style-border="true" height="150"]]** | ||
52 | |||
53 | To **change the user's email address**, the user must be **//deleted//** first. It can then be recreated with the new email address. | ||
54 | |||
55 | Under the Users menu, the **Lock/Unlock** function is available in the **More...** dropdown menu. This function is used to suspend a user account (which is a necessary step before deleting a profile). The status can be changed to locked or unlocked here. | ||
56 | |||
57 | Please keep in mind that a locked user can still receive notification emails. | ||
58 | |||
59 | (% class="aui-icon aui-icon-small aui-iconfont-warning confluence-embedded-file-wrapper confluence-embedded-manual-size confluence-information-macro-icon" %)[[image:attach:image-2023-4-25_16-31-30.png||data-xwiki-image-style-border="true" height="251" width="1000"]] | ||
60 | |||
61 | In order to **delete** a user, he / she **must be locked first** and must remain in locked status for a certain period of time. Since deletion is not reversible, It is suggested to //only lock// users rather than deleting the user profile. | ||
62 | |||
63 | The **Delete** option will present a confirmation. | ||
64 | |||
65 | An attempt to delete a locked user without being in locked state long enough will result in an error message: "This user has not yet spent enough time in Locked status to be deleted." | ||
66 | |||
67 | In case of a re-invited user, it is also possible to let the admin do the activation process instead of the user. To do so, click **Activate**. The user can still change the password later with the reset password option. Please refer to the [[Forgotten Passwords>>doc:DevOps Portal for Users.WebHome||anchor="HForgottenPassword" shape="rect" class="createlink"]] section of the DevOps Portal for Users page for details regarding forgotten passwords. | ||
68 | |||
69 | {{warning}} | ||
70 | ⚠ **Note** | ||
71 | A user can have 3 statuses in the Self-service Portal: **CREATED**, **ACTIVE** and **LOCKED**. In case there is a //question mark// or an //exclamation mark// shown in brackets right after the status name, there might be some synchronization issue. For more information about user statuses and troubleshooting, please have a look at the [[User statuses in DevOps Portal>>doc:DevOps Portal for Admins.User statuses in DevOps Portal.WebHome]] page. | ||
72 | {{/warning}} | ||
73 | |||
74 | |||
75 | = {{id name="creating_tech_users"/}}Creating Technical Users = | ||
76 | |||
77 | For automation tasks, technical users can be created. The technical user is bound to **one tool**. To create a technical user, access the **Technical Users **menu and click the **Create Technical User **button. | ||
78 | |||
79 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-25_16-33-59.png||data-xwiki-image-style-border="true" height="146" width="1000"]] | ||
80 | |||
81 | |||
82 | When creating a technical user, it is necessary to choose a **username** and to **select the tool**. It is recommended to choose a username that refers to the exact task or tool. The password is already pre-generated to be as secure as possible, but it can be manually changed (though not recommended). | ||
83 | |||
84 | //The description is optional for creating a technical user.// | ||
85 | |||
86 | [[image:attach:image-2023-5-11_13-0-43.png||data-xwiki-image-style-border="true" width="1000"]] | ||
87 | |||
88 | (% class="title" %) | ||
89 | [[image:attach:image-2023-5-11_13-1-59.png||data-xwiki-image-style-border="true" height="250"]] | ||
90 | |||
91 | |||
92 | = Modifying Technical User accounts = | ||
93 | |||
94 | |||
95 | [[image:attach:image-2023-4-25_16-41-23.png||data-xwiki-image-style-border="true" width="1000"]] | ||
96 | |||
97 | To view the details of a technical user, click its username. Tick the Edit Details box to make modifications to that user. | ||
98 | |||
99 | [[image:attach:image-2023-4-26_10-15-29.png||thumbnail="true" width="250"]] | ||
100 | |||
101 | It's also possible to change the tech user's password here. There is a minimum length required for passwords. | ||
102 | |||
103 | [[image:attach:image-2023-4-26_10-13-13.png||data-xwiki-image-style-border="true" width="500"]] | ||
104 | |||
105 | |||
106 | If you would like to change the username or the selected tool you have to **Delete** the user and recreate it again. The **Delete** option will present a confirmation. | ||
107 | |||
108 | |||
109 | = {{id name="manageorganizations"/}}Creating Organizations = | ||
110 | |||
111 | Per default, a user account is assigned to one organization (here in the example the default organization is //Manoni//). To add more organizations to a user account, click **Organizations **in the top menu and add a new organization by clicking **Create Organization**: | ||
112 | |||
113 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:07.jpg||data-xwiki-image-style-border="true" height="308" width="1000"]] | ||
114 | |||
115 | In the following example we create the fictional company //Wayne Corp//. | ||
116 | |||
117 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-26_10-19-0.png||data-xwiki-image-style-border="true" height="178" width="626"]] | ||
118 | |||
119 | |||
120 | After providing a name for your organization, click **Save** to create the new organization. | ||
121 | |||
122 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-26_10-19-40.png||data-xwiki-image-style-border="true" width="1000"]] | ||
123 | |||
124 | |||
125 | More organizations can be added by repeating these steps. | ||
126 | |||
127 | |||
128 | = Modify Organizations = | ||
129 | |||
130 | To modify an organization's profile, click the** organization name** (Wayne Corp in the example). | ||
131 | |||
132 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-26_10-22-47.png||data-xwiki-image-style-border="true" width="1000"]] | ||
133 | |||
134 | |||
135 | The **Edit an Organization page** will load and you can change the organization's name by replacing the name with the new one (so it is not necessary to delete an organization just because of the wrong name or a typo). As with the users edit page, the **Edit Details checkbox needs to be ticked **for editing to be enabled. | ||
136 | |||
137 | [[image:attach:image-2023-4-26_10-23-56.png||data-xwiki-image-style-border="true" height="161" width="573"]] | ||
138 | |||
139 | There is an option to **Delete** an organization, but keep in mind, that deleting an organization is not reversible. An organization cannot be deleted if at least one user is still assigned to the organization. The deletion process can be accessed from the Actions - More button. A confirmation will appear. | ||
140 | |||
141 | [[image:attach:image-2023-4-26_10-25-52.png||data-xwiki-image-style-border="true" height="122" width="1000"]] | ||
142 | |||
143 | The default organization is tied to the DevOps-as-a-Service instance and can never be renamed or deleted. | ||
144 | |||
145 | |||
146 | = Creating Projects = | ||
147 | |||
148 | In order to use the provided tools of DevOps services, first you have to create a project. Just Click on **Projects **in the top menu. | ||
149 | |||
150 | [[image:attach:image-2023-4-26_10-48-2.png||data-xwiki-image-style-border="true" height="250"]] | ||
151 | |||
152 | |||
153 | The list of projects will be loaded. If there isn't any project in the list, then one can be created easily: | ||
154 | |||
155 | To add a new project click **Create Project**: | ||
156 | |||
157 | [[image:attach:image-2023-4-26_10-48-56.png||data-xwiki-image-style-border="true" height="150"]] | ||
158 | |||
159 | |||
160 | Fill-in the following field: | ||
161 | |||
162 | **Project Key:** This identifier cannot be changed later and is used to identify the project in all tools. Letters and numbers are supported, but no special characters are allowed and it cannot start with a number. The portal will automatically display the Project Key in uppercase, but in some tools, it will appear in lowercase. | ||
163 | |||
164 | **Name:** This is the name of the project. Spaces are supported. | ||
165 | |||
166 | **Type:** The default value is PRIVATE, which means that members of the project will need to have a role assigned to gain access to the project. | ||
167 | |||
168 | **Tools:** These are the available tools that can be used in the toolchain by default. | ||
169 | |||
170 | **Description:** This is an optional field for a description of the project. | ||
171 | |||
172 | |||
173 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-26_13-15-45.png||data-xwiki-image-style-border="true" width="700"]] | ||
174 | |||
175 | |||
176 | Click **Save** to create the project. The list of projects will be reloaded and should contain the new project. If you would like to add more projects then repeat the previous step. | ||
177 | |||
178 | In the following example WI1 project has been added. | ||
179 | |||
180 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-26_13-17-23.png||data-xwiki-image-style-border="true" width="1000"]] | ||
181 | |||
182 | |||
183 | = {{id name="managingprojects"/}}Managing Projects = | ||
184 | |||
185 | To see or update the settings of a project, click the **Project Key** (WI1 in the example). Click **More ...** to open the actions menu. | ||
186 | |||
187 | [[image:attach:image-2023-4-26_14-56-35.png||data-xwiki-image-style-border="true" height="250"]] | ||
188 | |||
189 | |||
190 | When nobody works on a project anymore, the project can be //archived// by using **Retire.** A retired project cannot be accessed anymore, because all roles of the project will be removed from the associated tools. If you would like to use this project again you can **Reactivate **it. The project will then be {{code language="none"}}Active{{/code}} and usable again, but user roles have to be restored manually if necessary. | ||
191 | |||
192 | Retiring a project does not delete the project's data, it makes it inaccessible only. | ||
193 | |||
194 | If you would like to permanently remove a (retired) project, select **Delete** in the Actions menu (but keep in mind that a deleted project cannot be activated again, so it is suggested to just retire a project rather than deleting it). | ||
195 | |||
196 | {{error title="⚠ **Warning**"}} | ||
197 | (% style="color:#993300" %)Deleting a project is irreversible and project data will be lost! | ||
198 | {{/error}} | ||
199 | |||
200 | |||
201 | [[image:attach:image-2023-4-26_15-2-3.png||data-xwiki-image-style-border="true" height="400"]] | ||
202 | |||
203 | |||
204 | //**A project can only be deleted after having spent some time in the Retired status.**// | ||
205 | |||
206 | A **confirmation** is needed where you can type the project's name that you would like to delete and click on **Delete** button. | ||
207 | |||
208 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image2019-2-11_10-18-4.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="250"]] | ||
209 | |||
210 | |||
211 | = {{id name="assignusertoproject"/}}Assign a user to a project = | ||
212 | |||
213 | If you would like to add a user to a project Click **Users** in the top menu, then select the user from the list: | ||
214 | |||
215 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:02.jpg||data-xwiki-image-style-border="true" height="305" width="1000"]] | ||
216 | |||
217 | |||
218 | Select the **Project** and the **New Role** - one of **ADMIN, MASTER, DEVELOPER, VIEWER** (depending on the desired rights). After that, click **Assign**: | ||
219 | |||
220 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:03.jpg||data-xwiki-image-style-border="true" height="283" width="1000"]] | ||
221 | |||
222 | |||
223 | Each user who is a member of a project has to be in //exactly one// Project Role. Therefore it is not possible to have multiple roles in a project. | ||
224 | |||
225 | If you want to **Delete** a User from a project, simply select the **"-"** from the New Role dropdown menu. | ||
226 | |||
227 | Different roles have different sets of permissions. Possible roles are: | ||
228 | |||
229 | (% class="wrapped" %) | ||
230 | |=((( | ||
231 | Admin | ||
232 | )))|((( | ||
233 | (% class="content-wrapper" %) | ||
234 | ((( | ||
235 | Full access, even to potentially dangerous operations like Project Lifecycle Transitions. Can administer Project Members and Roles. | ||
236 | ))) | ||
237 | ))) | ||
238 | |=((( | ||
239 | Master | ||
240 | )))|((( | ||
241 | Limited full access to avoid accidental data loss or other irreversible changes. | ||
242 | ))) | ||
243 | |=((( | ||
244 | Developer | ||
245 | )))|((( | ||
246 | Read-write access to contribute to the Project | ||
247 | ))) | ||
248 | |=((( | ||
249 | Viewer | ||
250 | )))|((( | ||
251 | Read-only access to all not security-relevant data in the Project | ||
252 | ))) | ||
253 | |||
254 | Please refer to [[Users and roles>>doc:DevOps Portal for Admins.Users and roles.WebHome]] for a detailed description of users and roles in the tools. | ||
255 | |||
256 | = Viewing and Modifying the role of a user in a project = | ||
257 | |||
258 | If you would like to see the settings of a Project Member click **View** in the **More... **dropdown menu. | ||
259 | |||
260 | [[image:attach:04.jpg||data-xwiki-image-style-border="true" height="226" width="1000"]] | ||
261 | |||
262 | |||
263 | [[image:attach:05.jpg||data-xwiki-image-style-border="true" height="669" width="636"]] | ||
264 | |||
265 | In order to **modify** the roles of a project member, repeat the steps of [[Assign a user to a project>>||anchor="assignusertoproject"]] and select the new roles. | ||
266 | |||
267 | |||
268 | = Administration menu of the DevOps Portal = | ||
269 | |||
270 | In the Administration menu you can have special options to choose from, most of these features are for troubleshooting and monitoring. | ||
271 | |||
272 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image-2023-4-26_16-28-25.png||data-xwiki-image-style-border="true" thumbnail="true" height="250"]] | ||
273 | |||
274 | |||
275 | == Usage Terms == | ||
276 | |||
277 | With the "Usage Terms" option you can create and upload your own terms and condition documents about the usage of your own DevOps-as-a-Service toolchain. It is basically an option to provide any document to accept by the users (e.g. documents related to data protection regulations). | ||
278 | |||
279 | As an administrator, you can upload a document by selecting this option and clicking **Create new Terms**. | ||
280 | |||
281 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image2021-2-22_13-41-25.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="117" width="381"]] | ||
282 | |||
283 | Choose the preferred language, then click **Choose file**, browse the selected file from your local drive and click Open. | ||
284 | |||
285 | |||
286 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image2021-2-22_13-42-38.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="158" width="283"]] | ||
287 | |||
288 | The uploaded document is shown, you can check the content by clicking **Open**, remove the document by clicking **Delete**//,// or you can also **Cancel** the whole operation. If you would like to use the selected document, click **Save**. | ||
289 | |||
290 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image2021-2-22_13-47-46.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="229" width="610"]] | ||
291 | |||
292 | The selected document will be listed in the documents table and you will be logged out - to re-login and to accept the uploaded document. | ||
293 | |||
294 | (% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)[[image:attach:image2021-2-22_13-55-1.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="182" width="900"]] | ||
295 | |||
296 | After uploading a new terms and conditions document, every existing user has to accept it. Otherwise they are not allowed to login to the DevOps portal. | ||
297 | |||
298 | When new users are invited to the portal, they will receive the uploaded file as an attachment in the invitation mail (so they will be able to read it before following the activation URL). | ||
299 | |||
300 | //Every user (including administrators) have to accept// the uploaded document only one time, however if you upload another document then both documents have to be accepted by the users. | ||
301 | |||
302 | To remove an uploaded document, click **Delete**. If you would like to check the content of the uploaded document, click **View**. | ||
303 | |||
304 | //If you decide not to upload a document at all (or you delete all the existing uploaded documents) the invitation process and the login of users will not depend on the acceptance of any document, since nothing is to be accepted.// | ||
305 | |||
306 | == Synchronization == | ||
307 | |||
308 | All actions related to users or projects must be synchronized with the LDAP server prior to becoming effective. All pending (i.e. unfinished) synchronizations are listed at the **Pending synchronizations** page. Successful and finished synchronizations won't be listed. | ||
309 | |||
310 | This information is mainly provided for troubleshooting, in case of errors during the synchronization with the LDAP server. | ||
311 | |||
312 | [[image:attach:image-2023-5-11_13-59-28.png||data-xwiki-image-style-border="true" height="174" width="900"]] | ||
313 | |||
314 | == Health == | ||
315 | |||
316 | The Health page summarizes health checks for several components, such as the Database, the Disk space, the LDAP server and the Application. Depending on the actual service, more details might be available by clicking the eye symbol. | ||
317 | |||
318 | [[image:attach:image-2023-5-11_14-0-1.png||data-xwiki-image-style-border="true" height="258" width="900"]] | ||
319 | |||
320 | == Licenses == | ||
321 | |||
322 | The Licenses page provides information about the number of Active and Available Users as well as the package's User Limit. | ||
323 | |||
324 | [[image:attach:image-2023-5-11_14-0-37.png||data-xwiki-image-style-border="true" width="900"]] | ||
325 | |||
326 | == Audits == | ||
327 | |||
328 | Provides the audit log to check all past activities related to the Portal for up to 90 days. | ||
329 | |||
330 | [[image:attach:image-2023-5-11_14-2-46.png||data-xwiki-image-style-border="true" width="900"]] |