feat: configuration to allow/deny new customer registrations - #632
Merged
Conversation
BravoNatalie
approved these changes
Mar 24, 2026
BravoNatalie
left a comment
Contributor
There was a problem hiding this comment.
I think it’s okay to load the env var without following the usual pattern, given the current scenario
View stack outputs
|
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.
This PR adds a new environment var
DISABLE_CUSTOMER_REGISTRATIONwhich will disable customer registrations for the service when set to"true".There is a change to the rate limits storage to apply a block to all unknown customers. We don't really have a seperate registration flow to login, so this effectively disables regisrations (error message will say that account is blocked) at the point at which users try to "login" (
access/authorize). Otherwise a user would be able to login, but would then fail to register a plan and would not be able to provision a space.The customer store becomes read only when
DISABLE_CUSTOMER_REGISTRATIONis enabled, which prevents the OAuth and SSO sign in methods which side step theaccess/authorizeinvocation and also acts as a failsafe.