Skip to main content
Version: 3.4.0

Configuration

This page covers configuration options for the Apple identity provider beyond the basic setup.

Web Routes Configuration

Apple Sign-In requires web routes for handling callbacks and notifications. These routes must be configured both on Apple's side and in your Serverpod server.

The revokedNotificationRoutePath is the path that Apple will call when a user revokes their authorization. The webAuthenticationCallbackRoutePath is the path that Apple will call when a user completes the sign-in process.

These routes are configured in the pod.configureAppleIdpRoutes() method:

pod.configureAppleIdpRoutes(
revokedNotificationRoutePath: '/hooks/apple-notification',
webAuthenticationCallbackRoutePath: '/auth/callback',
);
  • revokedNotificationRoutePath (default: '/hooks/apple-notification'): The path Apple calls when a user revokes authorization. Register this URL in your Apple Developer Portal for server-to-server notifications.
  • webAuthenticationCallbackRoutePath (default: '/auth/callback'): The path Apple redirects to after the user completes web-based sign-in. Must match the return URL registered on your Service ID.
note

When a user revokes access from their Apple ID settings, Apple sends a notification to revokedNotificationRoutePath. Serverpod receives this notification automatically. You are responsible for invalidating any active sessions for that user in your own application logic.

Configuring Apple Sign-In on the app

Apple Sign-In requires additional configuration for web and Android platforms. On native Apple platforms (iOS/macOS), the configuration is handled automatically by the underlying sign_in_with_apple package through Xcode capabilities.

Passing configuration in code

You can pass the configuration directly when initializing the Apple Sign-In service:

client.auth.initializeAppleSignIn(
serviceIdentifier: 'com.example.app',
redirectUri: 'https://example.com/auth/callback',
);

The serviceIdentifier is your Apple Services ID (configured in Apple Developer Portal), and the redirectUri is the callback URL that Apple will redirect to after authentication (must match the URL configured on the server).

Both parameters are optional. If not supplied, the provider falls back to the corresponding --dart-define build variable:

  • serviceIdentifierAPPLE_SERVICE_IDENTIFIER
  • redirectUriAPPLE_REDIRECT_URI
note

These parameters are only required for web and Android platforms. On native Apple platforms (iOS/macOS), they are ignored, and the configuration from Xcode capabilities is used instead.

Using Environment Variables

Alternatively, you can pass configuration during build time using the --dart-define option:

  • APPLE_SERVICE_IDENTIFIER: The Apple Services ID.
  • APPLE_REDIRECT_URI: The redirect URI for authentication callbacks.

If you do not supply serviceIdentifier and redirectUri values when initializing the service, the provider will automatically fetch them from these environment variables.

Example usage:

flutter run \
-d "<device>" \
--dart-define="APPLE_SERVICE_IDENTIFIER=com.example.app" \
--dart-define="APPLE_REDIRECT_URI=https://example.com/auth/callback"

This approach is useful when you need to:

  • Manage configuration separately for different platforms (Android, Web) in a centralized way.
  • Avoid committing sensitive configuration to version control.
  • Configure different credentials for different build environments, like development, staging, and production.
tip

You can also set these environment variables in your IDE's run configuration or CI/CD pipeline to avoid passing them manually each time.

AppleIdpConfig parameter reference

ParameterTypeRequiredpasswords.yaml keyDescription
serviceIdentifierStringYes (Android/Web)appleServiceIdentifierThe Services ID identifier (e.g. com.example.service). Used as the OAuth client ID for Android and Web. Not required for iOS/macOS-only setups.
bundleIdentifierStringYesappleBundleIdentifierThe App ID bundle identifier (e.g. com.example.app). Used as the client ID for native Apple platform sign-in.
redirectUriStringYes (Android/Web)appleRedirectUriThe server callback route Apple redirects to after sign-in (e.g. https://example.com/auth/callback). Must be HTTPS and match the return URL registered on your Service ID.
teamIdStringYesappleTeamIdThe 10-character Team ID from your Apple Developer account (e.g. ABC123DEF4). Used to sign the client secret JWT.
keyIdStringYesappleKeyIdThe Key ID of the Sign in with Apple private key (e.g. XYZ789ABC0).
keyStringYesappleKeyThe raw contents of the .p8 private key file, including the -----BEGIN PRIVATE KEY----- header and footer. Serverpod uses this to generate a short-lived client secret JWT on each request. Do not pre-generate the JWT yourself.
webRedirectUriString?Web onlyappleWebRedirectUriThe web app URL that the browser is redirected to after the server receives Apple's callback. This is required when using the server callback route for Web.
androidPackageIdentifierString?Android onlyappleAndroidPackageIdentifierThe Android package name (e.g. com.example.app). When set, the callback route redirects Android clients back to the app via an intent URI using the signinwithapple scheme.

Environment Variable equivalents

All passwords.yaml keys can be set as environment variables by prefixing with SERVERPOD_PASSWORD_:

  • appleServiceIdentifierSERVERPOD_PASSWORD_appleServiceIdentifier
  • appleBundleIdentifierSERVERPOD_PASSWORD_appleBundleIdentifier
  • appleRedirectUriSERVERPOD_PASSWORD_appleRedirectUri
  • appleTeamIdSERVERPOD_PASSWORD_appleTeamId
  • appleKeyIdSERVERPOD_PASSWORD_appleKeyId
  • appleKeySERVERPOD_PASSWORD_appleKey
  • appleWebRedirectUriSERVERPOD_PASSWORD_appleWebRedirectUri
  • appleAndroidPackageIdentifierSERVERPOD_PASSWORD_appleAndroidPackageIdentifier