Permission, which represents an activity that requires a security privilege. This is usually a verb, like "configure", "administer", "tag", etc.
The Jenkins project takes security seriously. We make every possible effort to ensure users can adequately secure their automation infrastructure.
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
A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
Most users and developers will use these encryption keys indirectly via either the Secret API for encrypting generic secret data or through the credentials API.
Missing: /url | Show results with:/url
Content-Security-Policy is the name of a HTTP response header that modern browsers use to enhance the security of the document (or web page).
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
default-src 'none' prohibits loading scripts, URLs for AJAX/XHR/WebSockets/EventSources, fonts, plugin objects, media, and frames from anywhere (images and ...
Jenkins is a self-contained, open source automation server which can be used to automate all sorts of tasks related to building, testing, and delivering or ...
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 ...