Wiki source code of Automatically provided Credentials
Last modified by DevOps-as-a-Service Operator on 2025/02/05 11:33
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Jenkins can maintain credentials locally in the project folder of each project. Therefore, credentials of the different projects can be properly separated. To get to the credentials of your project, go to the home page of the DevOps Portal, then click on //Project Credentials// in the Jenkins tile. | ||
| 2 | |||
| 3 | [[image:attach:image-2024-3-15_15-39-2.png||queryparams="effects=drop-shadow" height="183" width="369"]] | ||
| 4 | |||
| 5 | The following screenshot shows the credentials of a project with the project key {{code language="none"}}tsolar.{{/code}} | ||
| 6 | |||
| 7 | [[image:attach:image-2024-3-15_15-45-50.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="372" width="529"]] | ||
| 8 | |||
| 9 | None of them should be changed nor deleted. If you do so by mistake, login to the DevOps Portal as a Portal Admin. Then simply edit and save the project again. This will recreate all technical users in the tools and add or update the credentials in the Jenkins project as necessary. You can use this also to rotate passwords at any time. | ||
| 10 | |||
| 11 | The following table explains all automatically provided credentials. The credentials are only provided for tools which are part of your DevOps-as-a-Service instance. Replace pkey by the project key of your project. | ||
| 12 | |||
| 13 | (% class="table-bordered" %) | ||
| 14 | (% class="active" %)|=((( | ||
| 15 | Credential Id and Username | ||
| 16 | )))|=((( | ||
| 17 | Credential Password contains | ||
| 18 | )))|=((( | ||
| 19 | Technical User in | ||
| 20 | )))|=((( | ||
| 21 | Role in Project | ||
| 22 | )))|=((( | ||
| 23 | Typical usage | ||
| 24 | ))) | ||
| 25 | |((( | ||
| 26 | pkey-jenkins | ||
| 27 | )))|((( | ||
| 28 | Password | ||
| 29 | )))|((( | ||
| 30 | Nexus | ||
| 31 | )))|((( | ||
| 32 | DEVELOPER | ||
| 33 | )))|((( | ||
| 34 | Push or pull artifacts from Nexus | ||
| 35 | ))) | ||
| 36 | |((( | ||
| 37 | pkey-git | ||
| 38 | )))|((( | ||
| 39 | Password | ||
| 40 | )))|((( | ||
| 41 | Bitbucket | ||
| 42 | )))|((( | ||
| 43 | VIEWER | ||
| 44 | )))|((( | ||
| 45 | Pull git repositories from Bitbucket | ||
| 46 | ))) | ||
| 47 | |((( | ||
| 48 | doaas-pkey+jenkins-push-harbor | ||
| 49 | )))|((( | ||
| 50 | Secret of a [[Harbor 2.7 Robot Account>>doc:Harbor.Harbor 2\.7 Robot Accounts.WebHome]] | ||
| 51 | )))|((( | ||
| 52 | Harbor | ||
| 53 | )))|((( | ||
| 54 | DEVELOPER | ||
| 55 | )))|((( | ||
| 56 | Push or pull artifacts from Harbor | ||
| 57 | ))) | ||
| 58 | |((( | ||
| 59 | pkey-jenkins-pull-gitea | ||
| 60 | )))|((( | ||
| 61 | [[Access Token>>doc:Gitea.Creating Access Tokens for Pushing Packages to Gitea.WebHome]] of a [[doc:Gitea.Gitea Technical Users.WebHome]] | ||
| 62 | )))|((( | ||
| 63 | Gitea | ||
| 64 | )))|((( | ||
| 65 | VIEWER | ||
| 66 | )))|((( | ||
| 67 | Pull git repositories or artifacts from Gitea | ||
| 68 | ))) | ||
| 69 | |((( | ||
| 70 | pkey-jenkins-push-gitea | ||
| 71 | )))|((( | ||
| 72 | [[Access Token>>doc:Gitea.Creating Access Tokens for Pushing Packages to Gitea.WebHome]] of a [[doc:Gitea.Gitea Technical Users.WebHome]] | ||
| 73 | )))|((( | ||
| 74 | Gitea | ||
| 75 | )))|((( | ||
| 76 | DEVELOPER | ||
| 77 | )))|((( | ||
| 78 | Push or pull git repositories or artifacts from Gitea | ||
| 79 | ))) |