fix generateSessionToken

[OrJDev]

NOTE:

• It's a good idea to open an issue first to discuss potential changes.
• Please make sure that you are NOT opening a PR to fix a potential security vulnerability. Instead, please follow the Security guidelines to disclose the issue to us confidentially.

☕️ Reasoning

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

Please scout and link issues that might be solved by this PR.

Fixes: INSERT_ISSUE_LINK_HERE

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

closes #6076

Looks like when passing the generateSessionToken an arrow function that calls the randomUUID function instead of passing the randomUUID function directly, solves this problem.

So instead of

myFunc: crypto.randomUUID

It should be

myFunc: () => crypto.randomUUID()

[vercel]

@OrJDev is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
auth-docs	❌ Failed (Inspect)			Dec 28, 2022 at 1:44PM (UTC)

[ndom91]

Strange, so I figure the initial way shuold have worked. Btw there was a small typo in your PR description above. It shuold be the following:

myFunc: crypto.randomUUID <-- function, not function call

it should be

myfunc: ()=> crypto.randomUUID()

In the rest of the adapter code, its always just called as myFunc() (for example).

[ndom91]

Testing it all in the a REPL though, this update looks correct. Calling it like myFunc() will then work correctly 👍

[OrJDev]

Ye i do have a typo I don't really know how to explain the changes because it makes absolutely no sense.
I expected the normal way to work as there is nothing that is messing with the binding in here.
Anyways im glad it works.