Changelog

New features

OAuth login — Google and Microsoft

Users can now register and authenticate using an existing Google or Microsoft account, eliminating the need for a separate email verification OTP.

New endpoints:

• POST /api/DigitalIdentity/Register/StepVerifyOAuthToken — verifies an OAuth ID token during registration and returns an oAuthTokenVerificationRequestId
• POST /api/DigitalIdentity/VerifyOAuthToken — verifies an OAuth token to skip email verification for an already-registered user

Updated endpoint:

• POST /api/DigitalIdentity/Register — now accepts oAuthTokenVerificationRequestId in the request body; providing it skips the email verification step

Supported providers:

• Google — configure client credentials in the Google Cloud Platform Console
• Microsoft — configure via Azure AD B2C

OAuth provider configuration is managed in the Vlens portal settings.

Example flow:

$
# 1 — Verify the OAuth token from Google/Microsoft
$
POST /api/DigitalIdentity/Register/StepVerifyOAuthToken
$
{
>
  "provider": "Google",
>
  "IdToken": "<id_token_from_google>"
>
}
$
$
# 2 — Register, skipping email OTP
$
POST /api/DigitalIdentity/Register
$
{
>
  "phoneNumber": "+201234567890",
>
  "oAuthTokenVerificationRequestId": "<guid_from_step_1>"
>
}