Last modified by Boris Folgmann on 2025/10/28 11:09

From version 7.2
edited by Martin Gurnik
on 2025/10/28 09:46
Change comment: There is no comment for this version
To version 7.3
edited by Martin Gurnik
on 2025/10/28 09:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,9 +7,10 @@
7 7  * If not done yet, set up a Technical User in the DevOps Portal for Rancher2 and assign it to the intended projects. Don't forget to record the password, you will not be able to see it later
8 8  * Log in to Rancher2 with the credentials of the Technical User. Since you need a different browser session for that, it's recommended to open an anonymous window in your browser for that.
9 9  * At the top right corner of the page, click on the icon ➡ and select Account & API Key
10 +* [[image:Screenshot 2025-10-28 at 10.41.31.png||height="226" width="466"]]
10 10  
11 - [[image:Screenshot 2025-10-28 at 10.41.31.png||height="226" width="466"]]
12 12  
13 +
13 13  * On the Account and API Keys page, click on "Create API Key"
14 14  * [[image:Screenshot 2025-10-28 at 10.41.42.png||height="432" width="752"]]
15 15  
... ... @@ -20,8 +20,10 @@
20 20  
21 21  
22 22  * [[image:Screenshot 2025-10-28 at 10.42.10.png||height="377" width="752"]]
23 -*
24 +
25 +
26 +
24 24  * Copy and record the created token for the intended use, then click SAVE.
25 25  * [[image:Screenshot 2025-10-28 at 10.42.21.png||height="484" width="790"]]
26 -* Log out
29 +* Note the details, because you will not be able to see them later
27 27  * Now Basic HTTP Authentication can be used with the username and the generated API Token (see [[https:~~/~~/www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/>>url:https://www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/]])