Repository navigation
Bugfix : Ensure emailVerified is not set to true in Spotify Auth sample - #1214
Merged
Merged
Conversation
jhuleatt
approved these changes
Oct 5, 2026
jhuleatt
left a comment
jhuleatt
left a comment
Contributor
There was a problem hiding this comment.
Spotify does not verify emails, so emailVerified must be false. Pushed a commit covering the updateUser path as well.
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
2 participants
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.
Problem
In the Spotify Auth sample,
customToken.emailVerifiedwas incorrectly set to true by default.However, Spotify API does not verify user emails. This creates a potential security vulnerability.
Solution
functions/index.jsto ensureemailVerifiedis either unset or explicitly set to false.Reference
Fixes #1154