Configure Sign in with Apple for Azure Static Web App

#azure edit this page

I’m working on a side project and decided to use Sign in with Apple as an additional authentication provider, next to AAD that I would normally use.

As per Microsoft’s documentation, adding apple as custom authentication provider is simple enough, just add the following lines to your staticwebapp.config.json file:

"identityProviders": {
    "apple": {
    "registration": {
        "clientIdSettingName": "APPLE_CLIENT_ID",
        "clientSecretSettingName": "APPLE_CLIENT_SECRET"

Then we add the two setting names to the Web App’s configuration and we’re done, right? Almost.

First we have to take a deep-dive into JWT as the APPLE_CLIENT_SECRET must be a signed JWT. There is no documentation specifically for Static Web Apps but this one for App Service is close enough.

I converted the sample C# code to powershell for easier use. The required package have a dependency loop and so, instead of easily installing them with Install-Package I had to use nuget. Follow the documentation above to obtain client id, team id, key id, and the key in pkcs8 format, then use the following snippet to generate the client secret:

function Get-AppleClientSecret {
    param (

    $p8Content = Get-Content -Path $p8keyfile
    $p8key = $p8Content.where{$_ -notmatch "^---"} -join("")

    [string]$audience = ""
    [string]$issuer = $teamId
    [string]$subject = $clientId
    [string]$kid = $keyId

    $Claims = New-Object -TypeName System.Collections.Generic.List[System.Security.Claims.Claim]
        (New-Object -TypeName System.Security.Claims.Claim("sub", $subject))
    $cngKey = [System.Security.Cryptography.CngKey]::Import(

    $signingCred = New-Object Microsoft.IdentityModel.Tokens.SigningCredentials(
        (New-Object Microsoft.IdentityModel.Tokens.ECDsaSecurityKey(
            (New-Object System.Security.Cryptography.ECDsaCng($cngKey)
        "ES256" # EcdsaSha256

    $NotBefore = Get-Date
    $Expires = (Get-Date).AddDays(180)
    $token = New-Object -TypeName System.IdentityModel.Tokens.Jwt.JwtSecurityToken(

    $null = $token.Header.Add("kid", $kid)
    $null = $token.Header.Remove("typ")

    $tokenHandler = New-Object System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler
    return $tokenHandler.WriteToken($token)

# install & import requirements
Invoke-WebRequest -Uri '' -OutFile "$env:USERPROFILE\Downloads\nuget.exe"
& "$env:USERPROFILE\Downloads\nuget.exe" Install System.IdentityModel.Tokens.Jwt -Version 6.32.0 -OutputDirectory "$env:USERPROFILE\Downloads\.nuget"

Add-Type -Path "$env:USERPROFILE\.nuget\packages\Microsoft.IdentityModel.Tokens\6.32.0\lib\netstandard2.0\Microsoft.IdentityModel.Tokens.dll"
Add-Type -Path "$env:USERPROFILE\.nuget\packages\System.IdentityModel.Tokens.Jwt\6.32.0\lib\netstandard2.0\System.IdentityModel.Tokens.Jwt.dll"
Add-Type -Path "$env:USERPROFILE\.nuget\packages\Microsoft.IdentityModel.Logging\6.32.0\lib\netstandard2.0\Microsoft.IdentityModel.Logging.dll"
Add-Type -Path "$env:USERPROFILE\.nuget\packages\Microsoft.IdentityModel.JsonWebTokens\6.32.0\lib\netstandard2.0\Microsoft.IdentityModel.JsonWebTokens.dll"
Add-Type -Path "$env:USERPROFILE\.nuget\packages\microsoft.identitymodel.abstractions\6.32.0\lib\netstandard2.0\Microsoft.IdentityModel.Abstractions.dll"

# set parameters and get secret
$p = @{
    TeamId = "Q847A7FG64"
    ClientId = "wtf.onprem.appleid"
    KeyId = "8QKD4J6XDZ"
    P8KeyFile = ".\AuthKey_8QKD4J6XDZ.p8"
Get-AppleClientSecret @p

Once we have obtained the APPLE_CLIENT_SECRET, the sign in process with Apple should be successful. However, after signing in, we are redirected to the Static Web App and greeted with a 403: Forbidden:

We need an email address or a handle from your login service. To use this login, please update your account with the missing info.

It turns out the identityProviders example given in Microsoft’s documentation is not quite complete. Sign in with Apple only inserts the user’s email address as claim in the authentication token if we specifically ask for it during the sing in process. To do that, we have to add the scopes property to the staticwebapp.config.json file:

"identityProviders": {
    "apple": {
    "registration": {
        "clientIdSettingName": "APPLE_CLIENT_ID",
        "clientSecretSettingName": "APPLE_CLIENT_SECRET"
    "login": {
        "scopes": ["email"]

Adding the scope will allow new users to sign in successfully. Users that had already signed in must first remove the app from Sign in with Apple in their Apple account.

So, after adding the scope and removing the app from Sign in with Apple, we can finally attempt to sign in again and we should see that the user has to consent sharing their email address in the sign in process: