Jenkins can expose a TCP port that allows inbound agents to connect to it. It can be enabled, disabled, and configured in Manage Jenkins » Security. The two ...
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
Plugins can provide additional security realms which may be useful for incorporating Jenkins into existing identity systems, such as: Active Directory.
This setting is controlled mainly by two axes: Security Realm, which determines users and their passwords, as well as what groups the users belong to.
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 ...
To change how quickly resource URLs expire, set the system property jenkins.security.ResourceDomainRootAction.validForMinutes to the desired value in minutes.
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 ...
default-src 'none' prohibits loading scripts, URLs for AJAX/XHR/WebSockets/EventSources, fonts, plugin objects, media, and frames from anywhere (images and ...
The Jenkins project takes security seriously. We make every possible effort to ensure users can adequately secure their automation infrastructure.
Missing: book/ | Show results with:book/
Permission, which represents an activity that requires a security privilege. This is usually a verb, like "configure", "administer", "tag", etc.