Conversation
…roxy This prevents token interceptions
WalkthroughThe oauth-proxy HelmRelease configuration within the kube-prometheus-stack was updated to explicitly set the OAuth2 code challenge method to "S256" in the OIDC provider configuration. No other aspects of the deployment or logic were changed. Changes
Suggested labels
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR enforces PKCE by setting the OAuth2 Proxy’s code_challenge_method to "S256", preventing token interception.
- Adds
code_challenge_method = "S256"to the OAuth2 Proxy configuration in the Helm chart. - Enhances security posture by enabling PKCE for all deployments.
Comments suppressed due to low confidence (1)
charts/base-cluster/templates/monitoring/kube-prometheus-stack/oauth-proxy.yaml:68
- Add or update a Helm chart test (e.g., using Chart Testing or a CI job) to assert that
code_challenge_methodis present and correctly rendered in the generated OAuth Proxy config.
code_challenge_method = "S256"
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
charts/base-cluster/templates/monitoring/kube-prometheus-stack/oauth-proxy.yaml (1)
68-68: Make PKCE method configurable and verify chart support
Consider exposingcode_challenge_methodvia a Helm value (e.g.,global.authentication.oauthProxy.codeChallengeMethod) and templating it with{{ .Values.global.authentication.oauthProxy.codeChallengeMethod | quote }}to allow future overrides. Additionally, verify that the Bitnamioauth2-proxychart version in use supports thecode_challenge_methodparameter to avoid compatibility issues.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
charts/base-cluster/templates/monitoring/kube-prometheus-stack/oauth-proxy.yaml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: generateDiffCommentBody
- GitHub Check: lint helm chart (base-cluster)
- GitHub Check: wait-for-checks
🔇 Additional comments (1)
charts/base-cluster/templates/monitoring/kube-prometheus-stack/oauth-proxy.yaml (1)
68-68: Explicit PKCE enforcement added
Explicitly settingcode_challenge_method = "S256"enforces a secure PKCE flow, mitigating authorization code interception attacks.
🤖 I have diffed this beep boop"/$namespace/$kind/$name.yaml" for normal resources
|
See <#1496> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enabled PKCE (Proof Key for Code Exchange) support for Grafana's OAuth authentication, enhancing security during login. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
🤖 I have created a release *beep* *boop* --- ## [8.1.0](base-cluster-v8.0.0...base-cluster-v8.1.0) (2025-06-06) ### Features * **base-cluster/monitoring:** allow upsizing tempo storage ([#1448](#1448)) ([db1a742](db1a742)) * **base-cluster/monitoring:** also read secrets for datasources ([#1479](#1479)) ([83ba8bd](83ba8bd)) * **base-cluster/monitoring:** configure service graph for grafana ([#1422](#1422)) ([8d4bb4c](8d4bb4c)) * **base-cluster/monitoring:** set code challenge for grafana ([#1500](#1500)) ([aa803da](aa803da)) * **base-cluster/monitoring:** set code_challenge_method for oauth2-proxy ([#1496](#1496)) ([b252cd7](b252cd7)) ### Bug Fixes * **base-cluster:** this prevents the user from installing this under another name ([#1418](#1418)) ([f4807e8](f4807e8)) ### Miscellaneous Chores * **base-cluster/docs:** update flux helmrelease command to update CRDs ([#1421](#1421)) ([a8fd535](a8fd535)) * **base-cluster/monitoring:** remove unnecessary open-telemetry-collector dashboard ([#1449](#1449)) ([520e9e1](520e9e1)) * **base-cluster:** change descheduler syntax ([#1483](#1483)) ([907bdae](907bdae)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced monitoring with support for upsizing tempo storage. - Enabled reading secrets for datasources and configuring the service graph in Grafana. - Added options to set the code challenge and code_challenge_method for Grafana and oauth2-proxy. - Introduced an optional persistence configuration for tracing ingester storage size. - **Bug Fixes** - Resolved an issue preventing installation of the chart under unintended names. - **Chores** - Updated helmrelease command for CRD updates. - Removed an unnecessary dashboard and adjusted descheduler syntax. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
This prevents token interceptions
Summary by CodeRabbit