Skip to content

chore: support verified domains for backend - #229

Open
b4s36t4 wants to merge 2 commits into
mainfrom
feat/sso-verified-email-domains
Open

b4s36t4 wants to merge 2 commits into
mainfrom
feat/sso-verified-email-domains

Conversation

@b4s36t4

@b4s36t4 b4s36t4 commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI balanced review requested due to automatic review settings October 13, 2026 06:41

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The configuration, template rendering, defaults, and documentation are consistent and complete.

0 open findings

What changed in this PR

Adds support for globally verified email domains in backend authentication workflows.

Changes:

  • Adds configurable verified domain lists with wildcard support.
  • Exposes domains through VERIFIED_EMAIL_DOMAINS.
  • Documents configuration and behavior.
File Description
charts/​portkey-app/​values.yaml Adds the domain configuration.
charts/​portkey-app/​templates/​_helpers.tpl Renders the backend environment variable.
charts/​portkey-app/​docs/​sso-setup.md Documents setup and supported use cases.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Copilot AI balanced review requested due to automatic review settings October 13, 2026 08:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The documented Secret alternatives are incomplete and cannot currently supply the domain value as described.

2 open findings

🧠 Review effort: Balanced

Comment on lines +150 to +151
- path: oauthVerifiedEmailDomains
objectAlias: oauthVerifiedEmailDomains
These domains:

* Are passed to the backend as the comma-separated `VERIFIED_EMAIL_DOMAINS` environment variable. This works with or without `config.existingSecretName`.
* Can alternatively come from a secret: leave `verifiedEmailDomains` empty and add an `oauthVerifiedEmailDomains` key (e.g. `acme.com,*.acme.io`) to the chart Secret / `existingSecretName` / your secret manager. If both are set, the `values.yaml` list wins.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants