Fix antiforgery token errors by restoring autoConfigureDataProtection in Azure Container Apps - #804
Merged
tjementum merged 1 commit intoDec 16, 2025
Conversation
tjementum
added
Bug
tjementum
removed
the
Deploy to Staging
…duce autoConfigureDataProtection Co-authored-by: Thomas Jespersen <tje@platformplatform.net>
tjementum
force-pushed
the
pp-670-antiforgery-token-error-in-azure-container-apps
branch
from
December 16, 2025 10:30
6c3fc2e to
6cc115f
Compare
tjementum
enabled auto-merge
December 16, 2025 10:33
tjementum
deleted the
pp-670-antiforgery-token-error-in-azure-container-apps
branch
December 16, 2025 10:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Upgrade the Azure Container Apps API version from
2025-07-01(stable) to2025-10-02-previewto restore theautoConfigureDataProtectionruntime setting for .NET containers.When upgrading to the stable
2025-07-01API version in PR #793, theautoConfigureDataProtectionfeature was inadvertently lost because it remains a preview-only feature not included in stable releases. This change reverts to a preview API version that supports this feature, which enables automatic configuration of ASP.NET Data Protection keys across all container apps in an environment - essential for antiforgery token validation when multiple container apps (AppGateway, account-management, back-office, etc.) need to share encrypted tokens.The learning here is that stable API versions may not include all preview features that the infrastructure depends on. When upgrading API versions, verify that preview features are still available or consciously choose to remain on a preview version until the required features become stable.
Checklist