Enable OAuth42-Managed Google and Apple Sign-In

Add Google or Apple to your OAuth42 hosted login page with a single toggle. OAuth42 manages the provider credentials, so you do not need to create or store them for your application.

When to use managed sign-in

Use this option when you want the fastest path to social sign-in on OAuth42 hosted authentication pages. Your application keeps its own OAuth42 client ID and redirect URIs, while OAuth42 supplies the upstream Google or Apple configuration.

You do not need: a Google Cloud OAuth client, a Google client secret, an Apple Services ID, or an Apple private key. Those are only required when you choose Custom Credentials instead.

Before you begin

  • An OAuth42 account with a configured application.
  • Your application is already using OAuth42 hosted authentication. See Getting Started with Hosted Authentication if it is not.
  • Google or Apple is available for your account. OAuth42 administrators configure and enable managed providers before they appear in the portal.

Step 1: Open your application's social providers

  1. Sign in to the OAuth42 Portal.
  2. Open Applications, then select the application whose hosted login page should offer the provider.
  3. Open the Social Providers tab.

Step 2: Turn on Google or Apple

At the top of the Social Providers tab, find Quick Start. Each available managed provider is labeled Managed by OAuth42.

  1. Find Google or Apple.
  2. Turn its toggle on.
  3. Confirm the card shows as enabled. No credential fields are required.

Provider not listed? The Quick Start section only shows providers that OAuth42 has configured and made available. Contact your OAuth42 administrator or support team to request Google or Apple; do not add the provider under Custom Credentials unless you intentionally want to manage your own credentials.

Step 3: Use your normal hosted sign-in flow

Start sign-in exactly as you already do for OAuth42 hosted authentication. The hosted login page reads the enabled providers for the application identified by your OAuth client ID and displays Google and/or Apple automatically.

Your app → OAuth42 hosted login → Google or Apple → OAuth42 callback → your registered redirect URI

There is no Google- or Apple-specific SDK integration to add to your app. Keep using your OAuth42 authorization flow and registered redirect URI.

Step 4: Test the hosted page

  1. Start a new sign-in for the application you changed.
  2. Confirm the hosted page displays Continue with Google or Sign in with Apple.
  3. Complete sign-in with a test provider account.
  4. Confirm OAuth42 returns the browser to your registered redirect URI and your application receives its normal OAuth42 session or tokens.

Apple note: Apple may provide a private relay email address, and it provides a user's name only on their first authorization. Treat both behaviors as normal.

Troubleshooting

The provider is not visible on the hosted page

Verify it is enabled in the Social Providers tab for the same application and that the authorization request uses that application's OAuth client ID. Start a fresh sign-in after changing the toggle.

Google or Apple is missing from Quick Start

The provider is not currently available as an OAuth42-managed provider for your account. Contact your OAuth42 administrator or support team.

I need my own consent screen, branding, or provider credentials

Use the Custom Credentials section instead. See the existing Google and Apple setup guides.