The permission Agent/Build requires access control for builds to be set up, as the build's authentication is checked, and not the user starting the build. In a ...
Missing: /url | Show results with:/url
A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
Jenkins access control is split into two parts: Authentication (users prove who they are) is done using a security realm. The security realm determines user ...
Security Realm, which determines users and their passwords, as well as what groups the users belong to. Authorization Strategy, which determines who has access ...
Missing: /url | Show results with:/url
This chapter will introduce the various security options available to Jenkins administrators and users, explaining the protections offered, and trade-offs to ...
Missing: /url | Show results with:/url
Administrators may accidentally set up a security realm or authorization strategy in such a way that they are no longer able to administer or even access ...
Missing: /url | Show results with:/url
User Documentation Home. User Handbook. User Handbook Overview · Installing Jenkins · Platform Information · Using Jenkins · Pipeline · Blue Ocean ...
Missing: /url | Show results with:/url
Docker Host Certificate Authentication credentials. Credential security. To maximize security, credentials configured in Jenkins are stored in an encrypted form ...
Jenkins is a self-contained, open source automation server which can be used to automate all sorts of tasks related to building, testing, and delivering or ...
Missing: book/ | Show results with:book/
Remote API can be used to do things like these: retrieve information from Jenkins for programmatic consumption. trigger a new build. create/copy jobs ...