feat: VK ID OAuth2 Provider
New VK ID OAuth2 Provider
OAuth VKontakte now is deprecated.
Obtaining a user access key (access token) is now possible only through OAuth VK ID.
That's exactly what I need.
Is there a reason why this can't just replace the old provider with a new major version?
Is there a reason why this can't just replace the old provider with a new major version?
Yes, there is. VK applications created earlier continue to work with the old provider.
OAuth VKontakte This is an outdated way of authorization using OAuth VKontakte. Getting a user Access token is now only possible through OAuth VK ID. At the same time, previously created applications with OAuth VKontakte are supported. If you need to work with the API on behalf of a community or public page, for example, so that the user can respond to community subscribers to messages, get a list of administered community identifiers through the user's Access token via OAuth 2.1, and then with this information get a community access key via OAuth VKontakte.
https://id.vk.com/about/business/go/docs/en/vkid/latest/oauth-vk#OAuth-VKontakte