A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
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
Docker Host Certificate Authentication credentials. Credential security. To maximize security, credentials configured in Jenkins are stored in an encrypted form ...
The security realm determines user identity and group memberships. Authorization (users are permitted to do something) is done by an authorization strategy.
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 ...
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 ...
Access to URLs provided by the security realm (to implement user signup or handle SSO authentication) ( /securityRealm/ ). agent.jar , remoting.jar , and ...
Remote API can be used to do things like these: retrieve information from Jenkins for programmatic consumption. trigger a new build. create/copy jobs ...
It is defined by the Jenkins URL specified in the global configuration. --httpsListenAddress=$HTTPS_HOST. Binds Jenkins to listen for HTTPS requests on the IP ...
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 ...