Content-Security-Policy. By default, Jenkins serves files that could come from less trusted sources with a strict Content-Security-Policy HTTP response header.
User Content. Jenkins has a mechanism known as "User Content", where administrators can place files inside $JENKINS_HOME/userContent , and these files ...
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 ...
A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
User Handbook · User Handbook Overview · Installing Jenkins · Platform Information · Using Jenkins · Pipeline · Blue Ocean · Managing Jenkins · Securing Jenkins ...
Missing: /url | Show results with:/url
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 ...
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/
Access to URLs provided by the security realm (to implement user signup or handle SSO authentication) ( /securityRealm/ ). agent.jar , remoting.jar , and ...
Use these instructions if your Jenkins configuration is not managed using Configuration as Code plugin or Groovy Init Hooks. The following steps will delete the ...