[Feature] OAuth / Laravel Socialite support with Sanctum

[mtzrmzia]

Is your feature request related to a problem? Please describe.

I’d like to use social login (Google, Facebook, etc.) via Laravel Socialite while still keeping session management with Sanctum and nuxt-auth-sanctum.
From what I can see in the documentation, the package currently only supports login using credentials (email/password), and there’s no mention of how to integrate Socialite or an OAuth2 flow. This makes it difficult to offer social login options while using this package.

Describe the solution you'd like

An approach or guide for integrating OAuth2 providers using Laravel Socialite along with Sanctum, so users can log in via social platforms and still benefit from cookie-based session handling in Nuxt.

Describe alternatives you've considered

• Manually handling Socialite redirects and then issuing Sanctum sessions with nuxt-auth-sanctum after login.
• Falling back to token-based authentication for social logins (but that defeats the purpose of using Sanctum with cookies).

Additional context

This would be especially useful for full-stack Nuxt apps that want to offer multiple login methods (email/password + social login) while using Sanctum’s cookie-based auth for simplicity and security.

[manchenkoff]

Hey @mtzrmzia!

Yes, this module was developed specifically for Sanctum integration since it is an independent Laravel package. And this was the main reason why it doesn't include functionality for other packages like Fortify, Socialite, Passport, etc. Usually, I create them separately, for instance - nuxt-laravel-echo, nuxt-sanctum-precognition.

However, it does not mean that you are limited to using only the login method. Behind the scenes, it is just a request against the API to get a cookie set in the response, and then refetching the user (which is accessible to call from your business logic).

As far as I know, Socialite uses a bit different approach for authenticating users, so maybe we can create a new module that can cover this particular functionality and can be easily integrated with the existing nuxt-auth-sanctum. Feel free to share more details about your use case or some code samples, it will help me understand the complexity of the task.

In the meantime, you can take a look at the existing Nuxt modules like https://github.com/Atinux/nuxt-auth-utils or https://github.com/sidebase/nuxt-auth since they provide an OAuth-compatible way of authentication.

[mtzrmzia]

@manchenkoff
Thanks for the reply. I’ve never implemented Socialite with Sanctum before, so I’m figuring it out step-by-step using the session + cookie-based setup.

My plan is:

• Use the standard dynamic redirect flow (/auth/redirect/{provider}) from Nuxt, via a popup or new window.
• Authenticate on the backend after the Socialite callback.
• Redirect back to the frontend and fetch the user via nuxt-auth-sanctum, assuming the laravel_session cookie was sent and stored by the browser.
• I’m not using tokens — only session-based auth with SESSION_DRIVER=database so I can later track active sessions/devices.

It’s my first time combining Socialite with Sanctum, so hopefully everything works out smoothly 😅.
I’ll keep reporting any progress or issues here.

Thanks for your work on this module 🙌