-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auth fails when used with Bicep template Microsoft.Web/staticSites/config@2022-03-01 #1076
Comments
Just thought I'd share that for 3 days last week, this deployment started to work. We briefly thought "great! It's fixed!". It turns out that was not the case; the issue started reoccurring this weekend. You can't see it, but so it doesn't get lost, we have this PR in place which illustrates this issue: We've got a deployed environment where it acts up: |
Is this related to #1089 (comment)? |
yes definitely. And I think the reason auth may be failing, is because it seems that SWAs can only support one method of configuration at a time. So either the SWA config or the Function App config. If the Function App config is in play, the config the SWA needs for auth is "missing" as far as the SWA is concerned. So it looks like auth is broken - it may actually just be as a result of SWAs only supporting 1 config at a time; function app or SWA |
Closing as was related to #1089 as suggested by @thomasgauvin |
Describe the bug
We use Bicep to deploy all of our Azure resources as an organisation. When upgrading one of our apps to use the latest Bicep templates, we uncovered an issue with the Microsoft.Web staticSites/config 'appsettings' 2022-03-01 Bicep template.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
staticwebapp.config.json
:staticwebapp.bicep
Expected behavior
Authentication should work.
Screenshots
N/A
Additional context
On February 14th 2023 I had a support call with Azure support person Sudarshan Yadav / [email protected] to diagnose this. The case number was 2302130050002282
We'd be happy to share application code; we're essentially using the approach documented by @rick-roche here:
https://www.rickroche.com/2022/03/single-sign-on-azure-static-web-apps-and-azure-active-directory/
The text was updated successfully, but these errors were encountered: