Support Auth Provider: Naver #35631

[theculturebrain]

Currently, Supabase supports Kakao login but not Naver login.

In the Korean market, Kakao and Naver have comparable user adoption. Supporting one while excluding the other makes little sense from a regional or product-market-fit perspective.

This is not a niche request. Naver login is a baseline requirement for many Korean services, and the lack of native support is a major blocker preventing Korean developers from adopting Supabase Auth.

Other auth solutions already support this out of the box (e.g. NextAuth does), so this is not a technical impossibility but a prioritization issue.

Yes, there are workarounds, but they are brittle, inconsistent, and undermine the simplicity that Supabase Auth is supposed to provide.

There have been multiple requests for Naver support over the past year with no official response. That silence is concerning, given Supabase’s stated goal of being a global-first platform.

If Supabase wants serious adoption in Korea, native Naver OAuth support is not optional — it’s table stakes.

Would appreciate a clear answer on whether this is planned, deprioritized, or explicitly out of scope.