OCPBUGS-115304:[release-5.0] bugfix: rewrite open redirect strings to '/'

[everettraven]

so that malformed redirect strings cannot result in an end-user being redirected to an unintended upstream application. This prevents leaking of authentication state information for the upstream application that oauth-proxy is being used as a reverse proxy for to an unintended audience.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@everettraven: This pull request references Jira Issue OCPBUGS-115304, which is invalid:

• expected Jira Issue OCPBUGS-115304 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

so that malformed redirect strings cannot result in an end-user being redirected to an unintended upstream application. This prevents leaking of authentication state information for the upstream application that oauth-proxy is being used as a reverse proxy for to an unintended audience.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9f80936a-52b4-45a0-9d8c-5cd7e0d22ae3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[everettraven]

/jira-refresh

[liouk]

/lgtm

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws
/test e2e-component

[ibihim]

/approve

[ibihim]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, ibihim, liouk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ibihim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@everettraven: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[everettraven]

/label backport-risk-assessed
/jira-refresh
/verified by @everettraven

[openshift-ci-robot]

@everettraven: This PR has been marked as verified by @everettraven.

Details

In response to this:

/label backport-risk-assessed
/jira-refresh
/verified by @everettraven

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.