A Security Realm which informs the Jenkins environment how and where to pull user (or identity) information from. Also commonly known as "authentication.".
Security Realm, which determines users and their passwords, as well as what groups the users belong to. Authorization Strategy, which determines who has access ...
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 security realm determines user identity and group memberships. Authorization (users are permitted to do something) is done by an authorization strategy.
Docker Host Certificate Authentication credentials. Credential security. To maximize security, credentials configured in Jenkins are stored in an encrypted form ...
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 ...
Remote API can be used to do things like these: retrieve information from Jenkins for programmatic consumption. trigger a new build. create/copy jobs ...
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 ...
To make scripted clients (such as wget) invoke operations that require authorization (such as scheduling a build), use HTTP BASIC authentication to specify the ...