I wrote recently about zero downtime deployments on Azure App Service. Many applications require authentication, and ours is no exception. In our case we're using Azure Active Directory facilitated by "Easy Auth" which provides authentication to our App Service.
Our app uses a Linux App Service. It's worth knowing that Linux App Services run as a Docker container. As a consequence, Easy Auth works in a slightly different way; effectively as a middleware. To quote the docs on Easy Auth:
This module handles several things for your app:
- Authenticates users with the specified provider
- Validates, stores, and refreshes tokens
- Manages the authenticated session
- Injects identity information into request headers The module runs separately from your application code and is configured using app settings. No SDKs, specific languages, or changes to your application code are required.
The authentication and authorization module runs in a separate container, isolated from your application code. Using what's known as the Ambassador pattern, it interacts with the incoming traffic to perform similar functionality as on Windows.
However, Microsoft have acknowledged there is a potential bug in Easy Auth support at present. When the app service is restarted, the stored tokens are removed, and authentication begins to fail. As you might well imagine, authentication similarly starts to fail when a new app service is introduced - as is the case during deployment.
This is really significant. You may well have "zero downtime deployment", but it doesn't amount to a hill of beans if the moment you've deployed your users find they're effectively logged out. The advice from Microsoft is to use Blob Storage for Token Cache:
Chris Gillum said in a blog on the topic:
you can provision an Azure Blob Storage container and configure your web app with a SaS URL (with read/write/list access) pointing to that blob container. This SaS URL can then be saved to the
WEBSITE_AUTH_TOKEN_CONTAINER_SASURLapp setting. When this app setting is present, all tokens will be stored in and fetched from the specified blob container.
To turn that into something visual, what's suggested is this:
SaS-sy ARM Templates
I have the good fortune to work with some very talented people. One of them, John McCormick turned his hand to putting this proposed solution into
azure-pipelines.yml and ARM template-land. First of all, let's look at our
azure-pipelines.yml. We add the following, prior to our deployment job:
- job: SASGen
displayName: Generate SAS Token
- task: AzurePowerShell@4
$startTime = Get-Date
$expiryTime = $startTime.AddDays(90)
$storageAcc = Get-AzStorageAccount -ResourceGroupName $(azureResourceGroup) -Name $(storageAccountName)
$ctx = $storageAcc.Context
$sas = New-AzStorageContainerSASToken -Context $ctx -Name "tokens" -Permission "rwl" -Protocol HttpsOnly -StartTime $startTime -ExpiryTime $expiryTime -FullUri
Write-Host "##vso[task.setvariable variable=sasToken;issecret=true;isOutput=true]$sas"
- job: DeployAppARMTemplates
sasToken: $[dependencies.SASGen.outputs['ObtainSasTokenTask.sasToken'] ]
displayName: Deploy App ARM Templates
- task: AzureResourceManagerTemplateDeployment@3
displayName: Deploy app-service ARM Template
deploymentScope: Resource Group
action: Create Or Update Resource Group
templateLocation: Linked artifact
There's two notable things happening above:
- In the
SASGenjob, a PowerShell script runs that generates a SaS token URL with read, write and list permissions that will last for 90 days. (Incidentally, there is a way to do this via ARM templates, and without PowerShell - but alas it didn't seem to work when we experimented with it.)
- The generated (secret) token URL (
sasUrl) is passed as a parameter to our App Service ARM template. The ARM template sets an appsetting for the app service:
If you google
WEBSITE_AUTH_TOKEN_CONTAINER_SASURL you will not find a geat deal. Documentation is short. What you will find is Jeff Sanders excellent blog on the topic. It is, in terms of content, it has some commonality with this post; except in Jeff's example he's manually implementing the workaround in the Azure Portal.
What's actually happening?
With this in place, every time someone logs into your app a JSON token is written to the storage like so:
If you take the trouble to look inside you'll find something like this tucked away:
With this in place, you can safely restart your app service and / or deploy a new one, safe in the knowledge that the tokens will live on in the storage account, and that consequently you will not be unauthenticating users.