Password Login Fixes #716
Merged
Password Login Fixes #716
Conversation
This file contains 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
|
+1 for hiding this behind an env flag! Best to isolate this behaviour from prod as much as possible |
Sounds good, it's only active with password auth and not fxa as that will always create new users. |
|
And added the env gate. |
devmount
approved these changes
Oct 11, 2024
MelissaAutumn
added a commit
that referenced
this pull request
Oct 15, 2024
* Adjust /token to create a user if one doesn't exist. Only works with password auth. * Add timezone to schedule for future-use (because we're collecting it right now..) * Gate the first time registration for password auth behind an env var.
This was referenced Oct 31, 2024
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.
Part of #120
This allows the password flow to create a new subscriber on first-login. But only first-login. (Well when there's no subscribers.)
Input wanted: Do we need to put this behaviour behind a env flag for extra security?
I discovered a fun bug with schedule creation/updates that causes it to fail because times are in UTC and 14:00 as a start-time is bigger than 0:00 as an end time. So we now collect timezones for schedules, and store them. (That'll be handy later!) We don't do anything else with them right now.