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 ...
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
Access to URLs provided by the security realm (to implement user signup or handle SSO authentication) ( /securityRealm/ ). agent.jar , remoting.jar , and ...
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 ...
Access Control · A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. · Authorization configuration ...
To maximize security, credentials configured in Jenkins are stored in an encrypted form on the controller Jenkins instance (encrypted by the Jenkins instance ID) ...
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 ...
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 ...
This section describes how to customize the rules restricting agents' access to the Jenkins controller in Jenkins 2.325 and earlier. In Jenkins 2.326, the ...
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/