Description: URL to which the browser will be redirected
user after clicking the “Login as” button.
It is important to indicate the address if you are using the scheme
authorization Connect.redirectAuth.
Thanks for informing us! I see the vk.com website still appears to be up. Are you saying that it will stop working at some point? When will it stop working?
Looks like the plugin is going to need an update to address this change.
VKontakte is switching to the vk.ru domain — all API integrations and authorizations will now only be available through it.
To ensure your services work correctly, change their domains by September 30 — for example:
• vk.ru/dev instead of vk.com/dev
• oauth.vk.ru instead of oauth.vk.com
• api.vk.ru instead of api.vk.com
For all questions, visit Support: dev.vk.com/ru/support
The domain has not stopped working, which is important for APIs and applications. They may discontinue support at any time. They gave notice on September 5 that everything had to be changed by September 30. It is still working, but may stop at any time.
VK in Russia is analogous to Facebook, while Yandex is analogous to Google, a major search engine and IT giant. If you were to consider adding Instant authorization for Yandex, it would be very convenient for all Russian-speaking users in Russia, the CIS, and around the world.
In order for the plugin to actually switch from vk.com to vk.ru, the plugin also needs to update the version of omniauth-vkontakto to include that commit, i.e. to be on version 1.9.0. I added this to your PR, but in practice, I don’t have any active sites running authentication via VK. Do you have one? Can you test the gem upgrade to see if it causes any issues?
VK Authentication no longer works, so this plugin is deprecated. You may like to try the community contributed VK ID OAuth 2.1 Authentication for Discourse plugin instead.
