Securing parametrized routers
Hi!
I want to generate a bunch of pages and that each belong to an individual outside of the application, lets call them customers. (Using T3)
So I have a parametrized route like this:
/[customerid].tsx
which needs to be easily accessible from an email sent to the customer. Confidentiality is not a life or death question but the higher it is the better (without sacrificing availability).
Is it enough to have a tricky [customerid] like a uuid/cuid and make sure its not indexed by search engines? Or would you add a passphrase on this page as an extra layer?
Thanks1 Reply
you can pass something like
/something/{uuid}?code={some-code-that-you-can-check}