Zoey

Hi @idesignzone 👋 If the token is returned in a different format then the current default you can use a json pointer to find it! ```ts // nuxt.config.ts { auth:...

Hi @gilles6 👋 This is going to be a pretty tricky bug to recreate and investigate. As I am not very familiar with Laravel Passport, I think it makes sense...

> Thank you very much for your reply, it finally worked but I can't remember why... Great to hear that it worked 💯 > I'm now stuck on how to...

> It needs to pass this Laravel route in routes/api.php file: When you make this fetch call (eg. in Postman) what would it look like? Do you need to set...

Hi @gilles6 👋 Sorry for the last reply here 😵 > However, async authorize is never passed. Any idea to fix this issue? I am a bit unsure in this...

Hi @gilles6, That sounds great! I am super happy you managed to find a solution! > Is it the correct way to deal with Laravel Passport access token? I am...

Hi @TiborPL 👋 From what I remember from the previous discussion, this limitation is due to NextAuth. We has thought about finding a way to add support through this, inside...

Closed in favor of #754

> It makes perfect sense to wait for a release of next-auth@5 which would also mean a release of a significant @auth/core version (maybe even v1). Agreed! I can see...

> Valid point regarding trustHost: https://github.com/sidebase/nuxt-auth/issues/691#issuecomment-1972763234 Primarily some missing security features, such as `trustHost`. Aside from this, we would definitely wait to deprecate the current version until authjs makes their...