Skip to content

feat: configuration to allow/deny new customer registrations - #632

Merged
alanshaw merged 5 commits into
mainfrom
ash/feat/disable-new-signups
Mar 25, 2026
Merged

feat: configuration to allow/deny new customer registrations#632
alanshaw merged 5 commits into
mainfrom
ash/feat/disable-new-signups

Conversation

@alanshaw

@alanshaw alanshaw commented Mar 24, 2026

Copy link
Copy Markdown
Member

This PR adds a new environment var DISABLE_CUSTOMER_REGISTRATION which 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_REGISTRATION is enabled, which prevents the OAuth and SSO sign in methods which side step the access/authorize invocation and also acts as a failsafe.

@alanshaw
alanshaw requested a review from a team March 24, 2026 12:32
@alanshaw alanshaw changed the title feat: configuration to allow/deny new signups to the service feat: configuration to allow/deny customer registrations Mar 24, 2026
@alanshaw alanshaw changed the title feat: configuration to allow/deny customer registrations feat: configuration to allow/deny new customer registrations Mar 24, 2026

@BravoNatalie BravoNatalie 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.

I think it’s okay to load the env var without following the usual pattern, given the current scenario

@seed-deploy
seed-deploy Bot temporarily deployed to pr632 March 25, 2026 11:15 Inactive
@seed-deploy
seed-deploy Bot temporarily deployed to pr632 March 25, 2026 11:18 Inactive
@seed-deploy

seed-deploy Bot commented Mar 25, 2026

Copy link
Copy Markdown
View stack outputs
  • pr632-warm-upload-api-BillingDbStack

    Name Value
    customerTableName pr632-warm-upload-api-customer
    egressTrafficMonthlyTableName pr632-warm-upload-api-egress-traffic-monthly
    egressTrafficTableName pr632-warm-upload-api-egress-traffic-events
    spaceDiffArchiveTableName pr632-warm-upload-api-space-diff-archive
    spaceDiffTableName pr632-warm-upload-api-space-diff
    spaceSnapshotTableName pr632-warm-upload-api-space-snapshot
    usageTable pr632-warm-upload-api-usage
  • pr632-warm-upload-api-BillingStack

    Name Value
    ApiEndpoint https://sgnqu34iu5.execute-api.us-east-2.amazonaws.com
    billingCronHandlerURL https://sbi3qpdtahsuv3fu3xbb63uxxm0wnszf.lambda-url.us-east-2.on.aws/
    CustomDomain https://pr632.billing.warm.storacha.network
    EgressTrafficQueueURL https://sqs.us-east-2.amazonaws.com/505595374361/pr632-warm-upload-api-egress-traffic-queue
  • pr632-warm-upload-api-CarparkStack

    Name Value
    BucketName pr632-warm-upload-api-carpark-0
    Region us-east-2
  • pr632-warm-upload-api-RoundaboutStack

    Name Value
    ApiEndpoint https://staging.roundabout.web3.storage/
    CustomDomain Using ROUNDABOUT_API_URL - no custom domain
  • pr632-warm-upload-api-UcanInvocationStack

    Name Value
    agentMessageBucketName pr632-warm-upload-api-workflow-store-0
  • pr632-warm-upload-api-UploadApiStack

    Name Value
    ApiEndpoints ["https://cmkch1alz5.execute-api.us-east-2.amazonaws.com"]
    CustomDomains ["https://pr632.up.warm.storacha.network"]
  • pr632-warm-upload-api-BusStack

  • pr632-warm-upload-api-FilecoinStack

  • pr632-warm-upload-api-UcanFirehoseStack

  • pr632-warm-upload-api-UploadDbStack

@alanshaw
alanshaw merged commit ed8da08 into main Mar 25, 2026
4 of 5 checks passed
@alanshaw
alanshaw deleted the ash/feat/disable-new-signups branch March 25, 2026 13:33
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