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 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 · 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 Control · A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. · Authorization configuration ...
The permission Agent/Build requires access control for builds to be set up, as the build's authentication is checked, and not the user starting the build. In a ...
Missing: /url | Show results with:/url
User Handbook · User Handbook Overview · Installing Jenkins · Platform Information · Using Jenkins · Pipeline · Blue Ocean · Managing Jenkins · Securing Jenkins ...
Missing: /url | Show results with:/url
To maximize security, credentials configured in Jenkins are stored in an encrypted form on the controller Jenkins instance (encrypted by the Jenkins instance ID) ...
The Jenkins project takes security seriously. We make every possible effort to ensure users can adequately secure their automation infrastructure.
To change how quickly resource URLs expire, set the system property jenkins.security.ResourceDomainRootAction.validForMinutes to the desired value in minutes.