OCPBUGS-93655: remote/azuread: use Secret type for OAuth client_secret [release-4.15]

[tonyxrmdavidson]

Fixes CVE-2026-42151 (GHSA-wg65-39gg-5wfj). OAuthConfig.ClientSecret was typed as a plain string, so it bypassed Prometheus's secret redaction and was exposed in plaintext via the
/api/v1/status/config API endpoint. Change it to config_util.Secret so it marshals to like other credentials.

[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]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-93655, which is invalid:

• expected Jira Issue OCPBUGS-93655 to depend on a bug targeting a version in 4.16.0, 4.16.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Fixes CVE-2026-42151 (GHSA-wg65-39gg-5wfj). OAuthConfig.ClientSecret was typed as a plain string, so it bypassed Prometheus's secret redaction and was exposed in plaintext via the
/api/v1/status/config API endpoint. Change it to config_util.Secret so it marshals to like other credentials.

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.

[openshift-ci]

@tonyxrmdavidson: 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.

[simonpasquier]

/restest-required

[simonpasquier]

we lack a valid dependent OCPBUGS ticket on release-4.16.

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-93655, which is invalid:

• expected Jira Issue OCPBUGS-93655 to depend on a bug targeting a version in 4.16.0, 4.16.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

/jira refresh

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.

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-93655, which is invalid:

• expected dependent Jira Issue OCPBUGS-93677 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

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.

Details

In response to this:

/jira refresh

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.

[tonyxrmdavidson]

/restest-required

[tonyxrmdavidson]

/restest-required

[simonpasquier]

/approve
/lgtm
/label backport-risk-assessed
/verified by @simonpasquier
/retest-required

[openshift-ci-robot]

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

Details

In response to this:

/approve
/lgtm
/label backport-risk-assessed
/verified by @simonpasquier
/retest-required

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.

[openshift-merge-bot]

Scheduling required tests:
/test e2e-agnostic-cmo
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: simonpasquier, tonyxrmdavidson

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 [simonpasquier]

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