-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out compatibility with NextAuth cookies supporting subdomains #5
Comments
The |
Do subdomains validate if you’re logged in to the root domain? That’s what
we need to get to.
…On Fri, Sep 23, 2022 at 4:18 PM sam-lippert ***@***.***> wrote:
The iss and domain properties are now set. Is this all that was needed?
—
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7QQXW5GLCVYAIUME3AXBTV7YNDNANCNFSM6AAAAAAQSC3T7I>
.
You are receiving this because you were assigned.Message ID: <drivly/oauth
.***@***.***>
|
Ok, the next step will be to validate cookies that are encrypted by NextAuth, because it doesn't use oauth.do for the cookie creation/encryption ... @crisner1978 now has a next-auth implementation that I believe is saving cookies to support subdomains at https://dev.driv.ly ... so @sam-lippert can you create a worker route in Cloudflare like test-auth.dev.driv.ly that could be then routed to the ctx-do worker to see if we can validate that? |
No description provided.
The text was updated successfully, but these errors were encountered: