I’m not saying we shouldn’t change this, just pointing out there’s a downside. If we want some folks to have a cleaner system log while no longer helping others to understand why their scripts start breaking after a long overdue update, we can easily change this.
The change that made existing scripts (using passwords and fixed crumbs) actively break went into 2.186/2.176.2: Upgrading to Jenkins LTS 2.176.x. The log improvement with a web page reference went into 2.220: Improve log after SECURITY-626 by Wadeck · Pull Request #4443 · jenkinsci/jenkins · GitHub