A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
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
Jenkins builds pull requests sent by untrusted users, or employ a security model that limits trust in users allowed to configure one or more jobs, this also ...
Credentials can be added to Jenkins by any Jenkins user who has the Credentials > Create permission (set through Matrix-based security). These permissions can ...
The procedures in this chapter are for new installations of Jenkins. Jenkins is typically run as a standalone application in its own process. The Jenkins WAR ...
Missing: authorization/ | Show results with:authorization/
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 ...
Remote API and security. When your Jenkins is secured, you can use HTTP BASIC authentication to authenticate remote API requests. See Authenticating scripted ...
Keep in mind that to run Jenkins as a service, the account that runs Jenkins must have permission to login as a service. Prerequisites. Minimum hardware ...
Missing: authorization/ | Show results with:authorization/