Kakao Login: Need for both REST API Key and Native App Key causes confusion

[MiryangJung]

Bug report

For Kakao Login, Android and iOS SDKs use the Native app key.
Currently, Supabase Dashboard requires inputting the REST API Key.

With the addition of Kakao OIDC support, login from Native apps has become possible,
but in this case, the Native app key needs to be entered in Supabase's REST API key field.

The reason for this is the code (if aud == clientID) that compares if the aud in the response matches the submitted key.

I believe this situation can be quite confusing because the documentation and dashboard use the term REST API Key.
(In fact, many Korean users utilizing Kakao login have been contacting me with questions about this 😅)

Here are my suggested solutions:

1. Allow for additional input of a Native App Key
   or
2. Change the term "REST API Key" to "Client ID" in both the documentation and dashboard, and update the Docs accordingly

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Not only the REST API Key, but the Native App Key has also become necessary.

Screenshots

System information

• Version of supabase-js: 2.45.3

Additional context

As this is beyond my authority, I'm seeking your guidance. Any advice on implementing these changes or direct assistance would be greatly appreciated.