/me endpoint not returning user.

[desert whale]

I've seen https://github.com/payloadcms/payload/discussions/10253
But I'm still not sure how I can return the user along with the /me endpoint when using custom strategy?
{"user":null,"message":"Account"}
Using oAuth: https://github.com/WilsonLe/payload-oauth2/blob/main/examples/google.ts

[lofty temple]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Authentication Operations - Me
• REST API - Custom Endpoints - Helpful tips
• Stripe Plugin - Endpoints - Stripe REST Proxy

Community-Help:

• REST api request specific data
• Filtering documents returned from localAPI using beforeRead hook.
• Env/environment variable undefined on deployments
• form builder plugin: forms are created but aren't accessed to render on frontend

[desert whale]

Not sure if anyone has any examples
Of doing this?

[solemn gazelle]

https://rubixstudios.com.au/insights/payloadcms-custom-auth-strategy

[desert whale]

Thanks @solemn gazelle are you seeing anything that below is not doing as to what you’ve suggested?

https://github.com/WilsonLe/payload-oauth2/blob/main/src/auth-strategy.ts

[solemn gazelle]

Ive seen most of these awhile ago, suggest you comment on the github project if you want advice for those.

But if you look at issues he's implementation doesn't work

😂 😂

[desert whale]

Oh really, where you seeing that

[solemn gazelle]

Goto the issue section and read his own notes.

[desert whale]

You got any recommendations on other oauth plugins?

[solemn gazelle]

Why, the article I gave you basically gives you the building block to create your own.

[desert whale]

Not sure if that issue is related to populating user info tho. Seems to be a reoccurring question. Not sure if it needs to be placed in after Me hook

[desert whale]

Just ease of use really, may need to add other strategies apart from google

[solemn gazelle]

😂 😂 If you actually look at my auth strategy on the site I have alot more but it follows the exact same similar flow.

[desert whale]

Can you make a plugin please 😂 nah jokes, so just to be sure, you’re basically plucking the user id from the jwt and doing a findbyid right?

[solemn gazelle]

I did mention on discord you'll probably be able to find it if you đo a search, the implementation I have is alot more complex. What I've written is secure to be used.

No

I the oauth calls the endpoint gets the token exchanges it verifies in the strategy creates a session based on verified. Jwt is to sign the payload token to assign it to the user cookies.

I've commented almost every line on the article.

[desert whale]

Oh okay so the session is responsible for grabbing user data ?

Appreciate it.

[solemn gazelle]

On the session is create to ensure the user is logged in

[desert whale]

I’m a bit lost mate, so what obtains user data when calling. /me?

[solemn gazelle]

The cookie that was created.

I think you're basing your integration on an integration where the guy who wrote it up specifically says he needs to add session auth into his implementation.

And I can see that's missing from the github.