ru_auth_providers

A Sails hook that registers the VK login provider in the @webresto/core auth layer and adds a settings page for it to the admin panel.

MAX and Telegram used to live here too. MAX moved to max-auth-adapter and Telegram to telegram_auth_provider, so that no two modules register the same provider slug.

VK

The VK ID / OAuth2 authorization-code flow. start redirects to oauth.vk.com/authorize with state set to the auth attempt id. VK returns to <AUTH_CALLBACK_BASE_URL>/auth/vk/callback, and complete exchanges the code for a token and reads the profile.

VK returns a phone only when the phone scope is granted, so the provider does not claim to verify phones (canVerifyPhone is not set) and requirePhoneVerification defaults to true: a VK sign-in goes through the SMS step.

Settings

The provider config is stored in AuthMethod.config and edited on the admin page, not in flat settings:

Key
clientId	VK application id
clientSecret	VK application secret
scope	requested scope, email by default

The core setting AUTH_CALLBACK_BASE_URL has to point at the public address of the server. The module also declares RU_AUTH_WEBHOOK_SECRET.

Admin panel

• Page: <routePrefix>/ru-auth-providers, access token ru-auth-providers.
• API: <routePrefix>/core/ru-auth-providers/{list,toggle,config,healthcheck}.

Install

Copy the folder into modules/ru_auth_providers of the application, then npm install and npm run build inside it.