Use same consent config with sdk and whitelabel#2471
Merged
chaitanyapotti merged 2 commits intomasterfrom May 11, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit fbd7a00. Configure here.
chaitanyapotti
approved these changes
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Jira Link
Description
Sdk config for consent required is not the same with whitelabel config (which configurable on dashboard also)
How has this been tested?
Screenshots (if appropriate)
Privacy and Terms links are showing now

Hover effects on accept button is fixed as well


Types of changes
Checklist
Note
Medium Risk
Changes the public consent configuration shape and the runtime gating for consent, which could break apps still using the old
uiConfig.consentConfigor expecting consent to trigger without policy/terms links.Overview
Unifies “consent required” configuration by removing
uiConfig.consentConfigand switching to top-leveluiConfig.consentRequiredplusprivacyPolicy/tncLinkacross the modal SDK and demo apps.Tightens consent behavior so consent is only treated as required when both
consentRequiredis true andprivacyPolicy/tncLinkare provided, and updatesWeb3Auth/LoginModalto deriveconsentRequiredfrom the modal instance duringinit.Includes a small UI tweak to the consent accept button hover/border styling and updates tests to match the new config.
Reviewed by Cursor Bugbot for commit d613770. Bugbot is set up for automated code reviews on this repo. Configure here.