Skip to content
Documentation

Data & backend

Social login

Let people sign in to your app with Google, Microsoft, or Apple. Google works straight away; with your own OAuth credentials the consent screen shows your app's name.

Give your users a one-tap sign-in with their Google, Microsoft, or Apple account. Google sign-in is on by default and works on Vorx's own Google client. For Microsoft and Apple you connect your own OAuth credentials, and you can do the same for Google, so the account chooser and consent screen show your app's name — not Vorx's.

You set this up in your project under Settings → Cloud → Social login. Each provider takes a few minutes the first time.

Before you start

  • You can test before you publish. Social sign-in works on your project's preview address as well as on your published *.vorx.live site or custom domain. If it doesn't complete inside the editor, open the preview in its own tab, or save your provider settings again under Settings → Cloud → Social login to re-apply the preview address.
  • Get access to each provider's developer console:
    • Google — the Google Cloud Console. Free.
    • Microsoft — a Microsoft account that belongs to a Microsoft Entra directory (tenant). A plain personal Microsoft account isn't enough on its own — see Get a Microsoft Entra directory below. Free, though Azure signup asks for a card to verify your identity.
    • Apple — the Apple Developer portal. Requires an active Apple Developer Program membership.

Set up Google

Settings → Cloud → Social login → Set up Google: the callback URL to add as a redirect URI, and the Client ID and secret fields

  1. In your project, open Settings → Cloud → Social login and choose Set up Google. Copy the Callback URL shown there — you'll need it in a moment.
  2. In the Google Cloud Console, go to Credentials → Create credentials → OAuth client ID, and pick Web application.
  3. Under Authorized redirect URIs, paste the Callback URL you copied from Vorx. It has to match exactly — scheme, domain, and path all count.
  4. Create the client, then copy its Client ID and Client secret back into Vorx and save.
  5. Reload your app's login page — Continue with Google now appears. Sign in on your published site to test it.

Set up Microsoft

Get a Microsoft Entra directory

Microsoft only lets you register apps inside an Entra directory. If you already sign in to Microsoft with a work or school account (for example, your company uses Microsoft 365), you have one — sign in to the Azure portal with that account and skip to the next section.

If you created a personal Microsoft account just for this, you'll see a warning on the App registrations page that "the ability to create applications outside of a directory has been deprecated." To fix it:

  1. Sign up for a free Azure account at azure.microsoft.com/free. This creates a directory for you. Microsoft asks for a phone number and a card to verify your identity; app registrations and Entra ID Free don't cost anything.
  2. Sign out of the Azure portal and sign back in.

The Microsoft 365 Developer Program is also suggested in that warning, but its free sandbox is now limited to eligible subscribers (such as Visual Studio Professional/Enterprise). Most new accounts see "You don't currently qualify", so use the Azure signup instead.

Register your app

  1. In Vorx, open Settings → Cloud → Social login, choose Set up Microsoft, and copy the Callback URL.
  2. In the Azure portal, open Microsoft Entra ID (on the home page, click View under Manage Microsoft Entra ID). In the left menu, go to Manage → App registrations → New registration.
  3. Give the app a name — this is what people see on the consent screen.
  4. Under Supported account types, choose the option that includes any organizational directory and personal Microsoft accounts. This matches Vorx's default and lets both work and personal accounts sign in. (Choose this directory only if you want to restrict sign-in to your own organization.)
  5. Under Redirect URI, choose Web and paste the Callback URL. Click Register.
  6. On the app's Overview page, copy the Application (client) ID.
  7. Open Certificates & secrets → Client secrets → New client secret, add a description and expiry, and click Add. Copy the secret's Value right away (not the Secret ID) — it's only shown once.
  8. Back in Vorx, paste the Application (client) ID and the secret value. Leave the Directory (tenant) URL on its default to allow any Microsoft account, or point it at your organization's tenant to restrict it.
  9. Save, reload your login page, and test Continue with Microsoft on your published site.

Microsoft client secrets expire (the portal defaults to 6 months, 24 months at most). Put a reminder in your calendar to create a new secret and paste it into Vorx before then, or sign-ins will start failing.

Set up Apple

  1. In Settings → Cloud → Social login, choose Set up Apple and copy the Callback URL.

  2. In the Apple Developer portal, create a Services ID — this is your Client ID. Enable Sign in with Apple for it and add the Callback URL as a Return URL.

  3. Create a Key with Sign in with Apple enabled and download the .p8 private key file — you only get one chance to download it. Note the Key ID shown, and your Team ID from the top of the Apple Developer site.

  4. Apple doesn't hand you a plain secret — you generate one yourself: a signed JWT built from your Team ID, Key ID, and the private key. See Supabase's guide for how to generate it, then paste the resulting JWT into Vorx as the Client secret, along with the Services ID as the Client ID.

  5. Save, reload your login page, and test Continue with Apple on your published site.

    Apple's secret expires after 6 months at most — put a reminder in your calendar to regenerate and re-paste it before then, or sign-ins will start failing silently.

Test it

Open your published app and click the new button. You'll be sent to Google, Microsoft, or Apple, see a consent screen with your app's name, and land back in your app already signed in. Buttons only show for providers you've turned on, so there's never a dead button.

Troubleshooting

  • "redirect_uri_mismatch" or a blank error after choosing an account — the Callback URL in Google/Microsoft/Apple doesn't exactly match the one Vorx shows. Re-copy it and check for a missing/extra trailing slash.
  • The button doesn't appear — make sure you saved the credentials, and reload the login page. Buttons are hidden until a provider is enabled.
  • It works on your live site but not the preview — if it doesn't complete inside the editor, open the preview in its own tab, or save your provider settings again under Settings → Cloud → Social login to re-apply the preview address.
  • Microsoft: can't find App registrations, or it says apps "outside of a directory" are deprecated — your Microsoft account isn't in an Entra directory yet. Follow Get a Microsoft Entra directory.
  • Microsoft: "Interaction required" / AADSTS16000 in the Azure portal — same cause: your personal account isn't a member of a directory. Sign up for Azure (or sign in with a work account), then sign out and back in.
  • Microsoft: personal accounts (Outlook, Hotmail) can't sign in — the app registration's Supported account types is set to your organization only. Change it under Authentication in the app registration, or create a new registration with the personal-accounts option.
  • Microsoft sign-in suddenly stops working — the client secret has probably expired. Create a new one under Certificates & secrets and paste it into Vorx.

Prefer to keep it simple? You can always stick with email and password — social login is an optional extra on top.