Jenkins now remembers the authorities (read group memberships) that the user had carried when he/she last time interactively logged in.
This information is exposed via User.impersonate(), which is used when using Jenkins SSH, Jenkins CLI, or access via API tokens.

Previously this was impossible for a subset of SecurityRealms that does not allow us to read group membership information without
successful login (such as Active Directory, OpenID, etc.)

For security reasons, if the backend determines that the user does not exist (as opposed to the backend who cannot tell if the user
exists or not), then the impersonation will fail.

I need to check AD plugin is reporting a failure correctly in this case, before marking as JENKINS-20064 fixed.

An unexpected failure in processing remember me cookie should be handled
gracefully. In particular, possibly problematic cookie should be
removed, or else the browser will keep bombarding the server with the
same cookie, and will never be able to get through.

It's much better to just drop the cookie.

This reverts commit 816f9d02.

Expose PrivateKeyProvider

Switch to java.util.logging on few places

[FIXED JENKINS-21969] Performance issue with search box

Improvements to the UpstreamCause

* Use model-links with context menu
* Show the display name of the linked job
* If the build isn't available, but the job is, still link to the job

[FIXED JENKINS-22080] Braindead logic in author of original fix... corre...

[FIXED JENKINS-22080] NPE if trying to install a plugin from the update ...

[FIXED JENKINS-22080] NPE if trying to install a plugin from the update center and either the update source or the plugin contains a '.' in its name

See https://github.com/kohsuke/winsw/commit/2ffdbde6a92cf582baa4137e7b4de1116a3ca88b