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
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
Securing Jenkins has two aspects to it. Access control, which ensures users are authenticated when accessing Jenkins and their activities are authorized.
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 ...
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/
User Documentation Home. User Handbook. User Handbook Overview · Installing Jenkins · Platform Information · Using Jenkins · Pipeline · Blue Ocean ...
Missing: /url | Show results with:/url
The following steps will delete the configuration for security realm and authorization strategy. Make sure you have a backup, to be able to restore the ...
Credentials can be added to Jenkins by any Jenkins user who has the Credentials > Create permission (set through Matrix-based security). These permissions can ...
Jenkins has a security mechanism in place so that the administrator of Jenkins can control who gets access to what part of Jenkins. The key components of this ...
Missing: book/ | Show results with:book/
Unmatched resilience, scalability & performance with CloudBees CI's High Availability mode