The following sections describe the access granted to users with (or without) the specified permissions. Default Permissions. Overall Permissions. These ...
The security realm determines user identity and group memberships. Authorization (users are permitted to do something) is done by an authorization strategy.
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
Access Control · A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. · Authorization configuration ...
Access Control · Security Realm, which determines users and their passwords, as well as what groups the users belong to. · Authorization Strategy, which ...
Missing: /url | Show results with:/url
Document Jenkins on Kubernetes. Security. Overview Security Advisories Reporting Vulnerabilities. About. Roadmap Press Awards Conduct Artwork · Download. Search ...
Missing: /url | Show results with:/url
Click OK to save the credentials. ⇐ Working with projects · ⇑ Using Jenkins Index · Search Box ⇒ ...
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 ...
Sharing a resource URL with another user, even one lacking Overall/Read permission for Jenkins, will grant that user access to these files until the URLs expire ...
Query the test-results of a completed build. Get objects representing the latest builds of a job. Search for artifacts by simple criteria. Block until jobs are ...