[JENKINS-73422] Add escape hatch for Authenticated user access to Resource URL

[Dohbedoh]

See JENKINS-73422 caused by #8922. Proposing an escape hatch to re-allow access to Resource URL. Many users seem impacted due to client automatically sending Authorization on redirect.. The escape hatch can help transitioning to the correct behavior while still upgrading Jenkins.

Testing done

Unit test.

Proposed changelog entries

• Add escape hatch for Authenticated user access to Resource URL

Proposed upgrade guidelines

To allow authenticated user to access Resource URL, add the system property jenkins.security.ResourceDomainRootAction.allowAuthenticatedUser=false on startup. This can also be done live by executing the groovy script jenkins.security.ResourceDomainRootAction.ALLOW_AUTHENTICATED_USER = true.

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@daniel-beck

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

[kmartens27]

@Dohbedoh would you be able to verify whether the jenkins.security.ResourceDomainRootAction.allowAuthenticatedUser=false should end with true instead? The upgrade guide entry was caught by @darinpope as it appears contradictory to the groovy script which does end in true. I just want to make sure so that the upgrade guide can be updated accordingly.

Thanks!

[Dohbedoh]

@kmartens27 you are right. I opened jenkins-infra/jenkins.io#7576