Authenticate Using Apple

You can let your users authenticate with Firebase using their Apple ID by using the Firebase SDK to carry out the end-to-end OAuth 2.0 sign-in flow.

Before you begin

To sign in users using Apple, first configure Sign In with Apple on Apple's developer site, then enable Apple as a sign-in provider for your Firebase project.

Join the Apple Developer Program

Sign In with Apple can only be configured by members of the Apple Developer Program.

Configure Sign In with Apple

  1. Enable Sign In with Apple for your app on the Certificates, Identifiers & Profiles page of Apple's developer site.
  2. Associate your website with your app as described in the first section of Configure Sign In with Apple for the web. When prompted, register the following URL as a Return URL: 
    https://YOUR_FIREBASE_PROJECT_ID.firebaseapp.com/__/auth/handler
     You can get your Firebase project ID on the Firebase console settings page. When you're done, take note of your new Service ID, which you'll need in the next section.
  3. Create a Sign In with Apple private key. You'll need your new private key and key ID in the next section.
  4. If you use any of Firebase Authentication's features that send emails to users, including email link sign-in, email address verification, account change revocation, and others, configure the Apple private email relay service and register noreply@YOUR_FIREBASE_PROJECT_ID.firebaseapp.com (or your customized email template domain) so Apple can relay emails sent by Firebase Authentication to anonymized Apple email addresses.

Enable Apple as a sign-in provider

  1. Add Firebase to your Apple project. Be sure to register your app's bundle ID when you set up your app in the Firebase console.
  2. In the Firebase console, open the Auth section. On the Sign in method tab, enable the Apple provider. Specify the Service ID you created in the previous section. Also, in the OAuth code flow configuration section, specify your Apple Team ID and the private key and key ID you created in the previous section.

Comply with Apple anonymized data requirements

Sign In with Apple gives users the option of anonymizing their data, including their email address, when signing in. Users who choose this option have email addresses with the domain privaterelay.appleid.com. When you use Sign In with Apple in your app, you must comply with any applicable developer policies or terms from Apple regarding these anonymized Apple IDs.

This includes obtaining any required user consent before you associate any directly identifying personal information with an anonymized Apple ID. When using Firebase Authentication, this may include the following actions:

  • Link an email address to an anonymized Apple ID or vice versa.
  • Link a phone number to an anonymized Apple ID or vice versa
  • Link a non-anonymous social credential (Facebook, Google, etc) to an anonymized Apple ID or vice versa.

The above list is not exhaustive. Refer to the Apple Developer Program License Agreement in the Membership section of your developer account to make sure your app meets Apple's requirements.

Sign in with Apple and authenticate with Firebase

To authenticate with an Apple account, first sign the user in to their Apple account using Apple's AuthenticationServices framework, and then use the ID token from Apple's response to create a Firebase AuthCredential object:

  1. For every sign-in request, generate a random string—a "nonce"—which you will use to make sure the ID token you get was granted specifically in response to your app's authentication request. This step is important to prevent replay attacks.

    You can generate a cryptographically secure nonce with SecRandomCopyBytes(_:_:_), as in the following example:

    Swift

    privatefuncrandomNonceString(length:Int=32)->String{
precondition(length > 0)
varrandomBytes=[UInt8](repeating:0,count:length)
leterrorCode=SecRandomCopyBytes(kSecRandomDefault,randomBytes.count,&randomBytes)
iferrorCode!=errSecSuccess{
fatalError(
"Unable to generate nonce. SecRandomCopyBytes failed with OSStatus \(errorCode)"
)
}
letcharset:[Character]=
Array("0123456789ABCDEFGHIJKLMNOPQRSTUVXYZabcdefghijklmnopqrstuvwxyz-._")
letnonce=randomBytes.map{bytein
// Pick a random character from the set, wrapping around if needed.
charset[Int(byte)%charset.count]
}
returnString(nonce)
}

    Objective-C

    // Adapted from https://auth0.com/docs/api-auth/tutorials/nonce#generate-a-cryptographically-random-nonce
- (NSString*)randomNonce:(NSInteger)length{
NSAssert(length > 0,@"Expected nonce to have positive length");
NSString*characterSet=@"0123456789ABCDEFGHIJKLMNOPQRSTUVXYZabcdefghijklmnopqrstuvwxyz-._";
NSMutableString*result=[NSMutableStringstring];
NSIntegerremainingLength=length;
while(remainingLength > 0){
NSMutableArray*randoms=[NSMutableArrayarrayWithCapacity:16];
for(NSIntegeri=0;i < 16;i++){
uint8_trandom=0;
interrorCode=SecRandomCopyBytes(kSecRandomDefault,1,&random);
NSAssert(errorCode==errSecSuccess,@"Unable to generate nonce: OSStatus %i",errorCode);
[randomsaddObject:@(random)];
}
for(NSNumber*randominrandoms){
if(remainingLength==0){
break;
}
if(random.unsignedIntValue < characterSet.length){
unicharcharacter=[characterSetcharacterAtIndex:random.unsignedIntValue];
[resultappendFormat:@"%C",character];
remainingLength--;
}
}
}
return[resultcopy];
}

    You will send the SHA256 hash of the nonce with your sign-in request, which Apple will pass unchanged in the response. Firebase validates the response by hashing the original nonce and comparing it to the value passed by Apple.

    Swift

    @available(iOS13,*)
privatefuncsha256(_input:String)->String{
letinputData=Data(input.utf8)
lethashedData=SHA256.hash(data:inputData)
lethashString=hashedData.compactMap{
String(format:"%02x",0ドル)
}.joined()
returnhashString
}

    Objective-C

    - (NSString*)stringBySha256HashingString:(NSString*)input{
constchar*string=[inputUTF8String];
unsignedcharresult[CC_SHA256_DIGEST_LENGTH];
CC_SHA256(string,(CC_LONG)strlen(string),result);
NSMutableString*hashed=[NSMutableStringstringWithCapacity:CC_SHA256_DIGEST_LENGTH*2];
for(NSIntegeri=0;i < CC_SHA256_DIGEST_LENGTH;i++){
[hashedappendFormat:@"%02x",result[i]];
}
returnhashed;
}

  2. Start Apple's sign-in flow, including in your request the SHA256 hash of the nonce and the delegate class that will handle Apple's response (see the next step):

    Swift

    importCryptoKit
// Unhashed nonce.
fileprivatevarcurrentNonce:String?
@available(iOS13,*)
funcstartSignInWithAppleFlow(){
letnonce=randomNonceString()
currentNonce=nonce
letappleIDProvider=ASAuthorizationAppleIDProvider()
letrequest=appleIDProvider.createRequest()
request.requestedScopes=[.fullName,.email]
request.nonce=sha256(nonce)
letauthorizationController=ASAuthorizationController(authorizationRequests:[request])
authorizationController.delegate=self
authorizationController.presentationContextProvider=self
authorizationController.performRequests()
}

    Objective-C

    @importCommonCrypto;
- (void)startSignInWithAppleFlow{
NSString*nonce=[selfrandomNonce:32];
self.currentNonce=nonce;
ASAuthorizationAppleIDProvider*appleIDProvider=[[ASAuthorizationAppleIDProvideralloc]init];
ASAuthorizationAppleIDRequest*request=[appleIDProvidercreateRequest];
request.requestedScopes=@[ASAuthorizationScopeFullName,ASAuthorizationScopeEmail];
request.nonce=[selfstringBySha256HashingString:nonce];
ASAuthorizationController*authorizationController=
[[ASAuthorizationControlleralloc]initWithAuthorizationRequests:@[request]];
authorizationController.delegate=self;
authorizationController.presentationContextProvider=self;
[authorizationControllerperformRequests];
}

  3. Handle Apple's response in your implementation of ASAuthorizationControllerDelegate. If sign-in was successful, use the ID token from Apple's response with the unhashed nonce to authenticate with Firebase:

    Swift

    @available(iOS13.0,*)
extensionMainViewController:ASAuthorizationControllerDelegate{
funcauthorizationController(controller:ASAuthorizationController,didCompleteWithAuthorizationauthorization:ASAuthorization){
ifletappleIDCredential=authorization.credentialas?ASAuthorizationAppleIDCredential{
guardletnonce=currentNonceelse{
fatalError("Invalid state: A login callback was received, but no login request was sent.")
}
guardletappleIDToken=appleIDCredential.identityTokenelse{
print("Unable to fetch identity token")
return
}
guardletidTokenString=String(data:appleIDToken,encoding:.utf8)else{
print("Unable to serialize token string from data: \(appleIDToken.debugDescription)")
return
}
// Initialize a Firebase credential, including the user's full name.
letcredential=OAuthProvider.appleCredential(withIDToken:idTokenString,
rawNonce:nonce,
fullName:appleIDCredential.fullName)
// Sign in with Firebase.
Auth.auth().signIn(with:credential){(authResult,error)in
iferror{
// Error. If error.code == .MissingOrInvalidNonce, make sure
// you're sending the SHA256-hashed nonce as a hex string with
// your request to Apple.
print(error.localizedDescription)
return
}
// User is signed in to Firebase with Apple.
// ...
}
}
}
funcauthorizationController(controller:ASAuthorizationController,didCompleteWithErrorerror:Error){
// Handle error.
print("Sign in with Apple errored: \(error)")
}
}

    Objective-C

    - (void)authorizationController:(ASAuthorizationController*)controller
didCompleteWithAuthorization:(ASAuthorization*)authorizationAPI_AVAILABLE(ios(13.0)){
if([authorization.credentialisKindOfClass:[ASAuthorizationAppleIDCredentialclass]]){
ASAuthorizationAppleIDCredential*appleIDCredential=authorization.credential;
NSString*rawNonce=self.currentNonce;
NSAssert(rawNonce!=nil,@"Invalid state: A login callback was received, but no login request was sent.");
if(appleIDCredential.identityToken==nil){
NSLog(@"Unable to fetch identity token.");
return;
}
NSString*idToken=[[NSStringalloc]initWithData:appleIDCredential.identityToken
encoding:NSUTF8StringEncoding];
if(idToken==nil){
NSLog(@"Unable to serialize id token from data: %@",appleIDCredential.identityToken);
}
// Initialize a Firebase credential, including the user's full name.
FIROAuthCredential*credential=[FIROAuthProviderappleCredentialWithIDToken:IDToken
rawNonce:self.appleRawNonce
fullName:appleIDCredential.fullName];
// Sign in with Firebase.
[[FIRAuthauth]signInWithCredential:credential
completion:^(FIRAuthDataResult*_NullableauthResult,
NSError*_Nullableerror){
if(error!=nil){
// Error. If error.code == FIRAuthErrorCodeMissingOrInvalidNonce,
// make sure you're sending the SHA256-hashed nonce as a hex string
// with your request to Apple.
return;
}
// Sign-in succeeded!
}];
}
}
-(void)authorizationController:(ASAuthorizationController*)controller
didCompleteWithError:(NSError*)errorAPI_AVAILABLE(ios(13.0)){
NSLog(@"Sign in with Apple errored: %@",error);
}

Unlike other providers supported by Firebase Auth, Apple does not provide a photo URL.

Also, when the user chooses not to share their email with the app, Apple provisions a unique email address for that user (of the form xyz@privaterelay.appleid.com), which it shares with your app. If you configured the private email relay service, Apple forwards emails sent to the anonymized address to the user's real email address.

Reauthentication and account linking

The same pattern can be used with reauthenticateWithCredential(), which you can use to retrieve a fresh credential for sensitive operations that require recent sign-in:

Swift

// Initialize a fresh Apple credential with Firebase.
letcredential=OAuthProvider.credential(
withProviderID:"apple.com",
IDToken:appleIdToken,
rawNonce:rawNonce
)
// Reauthenticate current Apple user with fresh Apple credential.
Auth.auth().currentUser.reauthenticate(with:credential){(authResult,error)in
guarderror!=nilelse{return}
// Apple user successfully re-authenticated.
// ...
}

Objective-C

FIRAuthCredential*credential=[FIROAuthProvidercredentialWithProviderID:@"apple.com",
IDToken:appleIdToken,
rawNonce:rawNonce];
[[FIRAuthauth].currentUser
reauthenticateWithCredential:credential
completion:^(FIRAuthDataResult*_NullableauthResult,
NSError*_Nullableerror){
if(error){
// Handle error.
}
// Apple user successfully re-authenticated.
// ...
}];

And, you can use linkWithCredential() to link different identity providers to existing accounts.

Note that Apple requires you to get explicit consent from users before you link their Apple accounts to other data.

Sign in with Apple will not allow you to reuse an auth credential to link to an existing account. If you want to link a Sign in with Apple credential to another account, you must first attempt to link the accounts using the old Sign in with Apple credential and then examine the error returned to find a new credential. The new credential will be located in the error's userInfo dictionary and can be accessed via the AuthErrorUserInfoUpdatedCredentialKey key.

For example, to link a Facebook account to the current Firebase account, use the access token you got from signing the user in to Facebook:

Swift

// Initialize a Facebook credential with Firebase.
letcredential=FacebookAuthProvider.credential(
withAccessToken:AccessToken.current!.tokenString
)
// Assuming the current user is an Apple user linking a Facebook provider.
Auth.auth().currentUser.link(with:credential){(authResult,error)in
// Facebook credential is linked to the current Apple user.
// The user can now sign in with Facebook or Apple to the same Firebase
// account.
// ...
}

Objective-C

// Initialize a Facebook credential with Firebase.
FacebookAuthCredential*credential=[FIRFacebookAuthProvidercredentialWithAccessToken:accessToken];
// Assuming the current user is an Apple user linking a Facebook provider.
[FIRAuth.authlinkWithCredential:credentialcompletion:^(FIRAuthDataResult*_NullableauthResult,NSError*_Nullableerror){
// Facebook credential is linked to the current Apple user.
// The user can now sign in with Facebook or Apple to the same Firebase
// account.
// ...
}];

Token revocation

Apple requires that apps that support account creation must let users initiate deletion of their account within the app, as described in the App Store Review Guidelines

To meet this requirement, implement the following steps:

  1. Make sure you filled out the Services ID and OAuth code flow configuration section of the Sign in with Apple provider configuration, as outlined in the Configure Sign in with Apple section.

  2. Since Firebase does not store user tokens when users are created with Sign in with Apple, you must ask the user to sign in again before revoking their token and deleting the account.

    Swift

    privatefuncdeleteCurrentUser(){
do{
letnonce=tryCryptoUtils.randomNonceString()
currentNonce=nonce
letappleIDProvider=ASAuthorizationAppleIDProvider()
letrequest=appleIDProvider.createRequest()
request.requestedScopes=[.fullName,.email]
request.nonce=CryptoUtils.sha256(nonce)
letauthorizationController=ASAuthorizationController(authorizationRequests:[request])
authorizationController.delegate=self
authorizationController.presentationContextProvider=self
authorizationController.performRequests()
}catch{
// In the unlikely case that nonce generation fails, show error view.
displayError(error)
}
}

  3. Obtain the authorization code from the ASAuthorizationAppleIDCredential, and use it to call Auth.auth().revokeToken(withAuthorizationCode:) to revoke the user's tokens.

    Swift

    funcauthorizationController(controller:ASAuthorizationController,
didCompleteWithAuthorizationauthorization:ASAuthorization){
guardletappleIDCredential=authorization.credentialas?ASAuthorizationAppleIDCredential
else{
print("Unable to retrieve AppleIDCredential")
return
}
guardlet_=currentNonceelse{
fatalError("Invalid state: A login callback was received, but no login request was sent.")
}
guardletappleAuthCode=appleIDCredential.authorizationCodeelse{
print("Unable to fetch authorization code")
return
}
guardletauthCodeString=String(data:appleAuthCode,encoding:.utf8)else{
print("Unable to serialize auth code string from data: \(appleAuthCode.debugDescription)")
return
}
Task{
do{
tryawaitAuth.auth().revokeToken(withAuthorizationCode:authCodeString)
tryawaituser?.delete()
self.updateUI()
}catch{
self.displayError(error)
}
}
}

  4. Finally, delete the user account (and all associated data)

Next steps

After a user signs in for the first time, a new user account is created and linked to the credentials—that is, the user name and password, phone number, or auth provider information—the user signed in with. This new account is stored as part of your Firebase project, and can be used to identify a user across every app in your project, regardless of how the user signs in.

  • In your apps, you can get the user's basic profile information from the User object. See Manage Users.

  • In your Firebase Realtime Database and Cloud Storage Security Rules, you can get the signed-in user's unique user ID from the auth variable, and use it to control what data a user can access.

You can allow users to sign in to your app using multiple authentication providers by linking auth provider credentials to an existing user account.

To sign out a user, call signOut:.

Swift

letfirebaseAuth=Auth.auth()
do{
tryfirebaseAuth.signOut()
}catchletsignOutErrorasNSError{
print("Error signing out: %@",signOutError)
}

Objective-C

NSError*signOutError;
BOOLstatus=[[FIRAuthauth]signOut:&signOutError];
if(!status){
NSLog(@"Error signing out: %@",signOutError);
return;
}

You may also want to add error handling code for the full range of authentication errors. See Handle Errors.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025年10月31日 UTC.