×
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 ...
Sep 7, 2021 · 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 ...
Missing: book/ | Show results with:book/
When your Jenkins is secured, you can use HTTP BASIC authentication to authenticate remote API requests. See Authenticating scripted clients for more details.
> User Documentation Home. User Handbook. User Handbook ... Securing Jenkins · System Administration · Scaling ... Authenticating scripted clients · Reverse proxy ...
Missing: /url | Show results with:/url
Authenticating scripted clients · Reverse proxy configuration · Reverse proxy - Issues · Managing systemd services · FIPS-140 · Reset the Jenkins administrator ...
Missing: /url | Show results with:/url
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 ...
A 'reverse proxy' allows an alternate HTTP or HTTPS provider to communicate with web browsers on behalf of Jenkins. The alternate provider may offer ...
Access to URLs provided by the security realm (to implement user signup or handle SSO authentication) ( /securityRealm/ ). agent.jar , remoting.jar , and ...
Jenkins has a built-in command line interface that allows users and administrators to access Jenkins from a script or shell environment.
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