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
Administrators may accidentally set up a security realm or authorization strategy in such a way that they are no longer able to administer or even access ...
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 ...
Remote API can be used to do things like these: retrieve information from Jenkins for programmatic consumption. trigger a new build. create/copy jobs ...
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: /url book/ authorization/
Management tasks such as configuration, authorization, and authentication are executed on the controller, which serves HTTP requests. Files written when a ...
Using Build Tools ... Keep in mind that to run Jenkins as a service, the account that runs Jenkins must have permission to login as a service. ... Security Policy.
To make scripted clients (such as wget) invoke operations that require authorization (such as scheduling a build), use HTTP BASIC authentication to specify the ...
Jenkins has a built-in command line interface that allows users and administrators to access Jenkins from a script or shell environment.