Hi, I'm planning to use our Descope auth in our do...
# ask-a-descoper
p
Hi, I'm planning to use our Descope auth in our docs site. Initially, I was thinking of using a subdomain, like
<http://docs.example.com|docs.example.com>
, assuming our main domain is
<http://example.com|example.com>
. I read https://docs.descope.com/how-to-deploy-to-production/custom-domain#example and I’m wondering whether using
<http://example.com/docs|example.com/docs>
instead would simplify cookie handling and authentication overall. It’s important to note that
<http://example.com|example.com>
is a Next.js application, while
<http://docs.example.com|docs.example.com>
is an AstroJS application. From your experience, what would be the recommended approach in this case? thank you!
a
Hey Pablo! You can share tokens across subdomains, so that sessions would carry over for both the docs subdomain and the root domain.
p
thank you @Avi Glozman