Click your name on the top right corner on every page, then click "Configure" to see your API token. (The URL $root/me/configure is a good shortcut.) You can ...
When your Jenkins is secured, you can use HTTP BASIC authentication to authenticate remote API requests. See Authenticating scripted clients for more details.
Jenkins Handbook · User Handbook Overview · Installing Jenkins · Docker · Kubernetes · Platform Information · Java Support Policy · Linux Support Policy · Using ...
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 ...
Missing: scripted- | Show results with:scripted-
Authenticating scripted clients · Reverse proxy configuration · Reverse proxy - Issues · Managing systemd services · FIPS-140 · Reset the Jenkins administrator ...
Missing: /url | Show results with:/url
Viewing logs · Logs on the system · Logs in Jenkins · Making custom logs available outside of the web UI · Debug logging in Jenkins.
Authenticating scripted clients · Reverse proxy ... System Configuration matches the URL you're using to access Jenkins. ... For example, the URL https://jenkins.
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
A 'reverse proxy' allows an alternate HTTP or HTTPS provider to communicate with web browsers on behalf of Jenkins. The alternate provider may offer ...
Jenkins installs "ping thread" on every remoting connection, such as controller/agent connections, regardless of its transport mechanism (such as SSH, JNLP, ...