Skip to content

auth.third_party.clerk unable to add multiple domains #4679

@jameslshannon

Description

@jameslshannon

Describe the bug
Supabase.com allows multiple domains to be added for a third party auth provider such as Clerk. The use case is where multiple apps share the same Supabase db but have differing auth configurations in Clerk (and therefore different Clerk domains).

To Reproduce
Steps to reproduce the behavior:

  1. Add a domain in config.toml under [auth.third_party.clerk]
  2. Add another domain in config.toml under [auth.third_party.clerk]
  3. Run npx supabase stop
  4. See error config: toml: key domain is already defined

Expected behavior
Multiple domains should be supported under [auth.third_party.clerk] - either as multiple domain entries or to allow domain to specify an array of domains in order to replicate the online Supabase configuration, thereby allowing multiple local apps to run that require different Clerk domains.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions