If the resource root URL is defined, Jenkins will instead redirect requests for user-created resource files to URLs starting with the URL configured here. These ...
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
User Content. Jenkins has a mechanism known as "User Content", where administrators can place files inside $JENKINS_HOME/userContent , and these files ...
A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
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 ...
User Handbook · User Handbook Overview · Installing Jenkins · Platform Information · Using Jenkins · Pipeline · Blue Ocean · Managing Jenkins · Securing Jenkins ...
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
Welcome to the Jenkins user documentation - for people wanting to use Jenkins's existing functionality and plugin features. If you want to extend the ...
Missing: book/ | Show results with:book/
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 ...
Permission, which represents an activity that requires a security privilege. · Authentication , which represents the current user and roles (AKA groups) he/she ...
Missing: book/ | Show results with:book/