I rarely if ever comment a UA-cam video (unthankful ass). But I have to: This video made my deployment work on the first run including AAD (tenant specific) authentication! Thank you, very on point!
Thanks, Doug. This really helped me. For some reason, the manifest.json linked in the index.html causes unintentional redirects whenever I try to add any type of authentication. I just removed it and that helped me for now. Weird how this doesn't come up in your example, making me think this could be something specific to my organizational tenant.
How do you ensure unique content for each logged in user? I think some real world example with more popular react framework such as nextjs or remixjs would help a lot.
Thanks for putting this video together. For some reason, the `staticwebapp.config.json` file isn't being respected. I pasted the same values you did from the MS Learn page, but there is no auth being enforced when I open the page, even in an incognito window. Do you have any thoughts on this one?
Hm...yeah. I just re-created the Azure Static Web App, upgraded to Standard plan, created the `staticwebapp.config.json` file, same issue. I can't get the route /* to work. The website loads with no auth prompt. I'm using `mkdocs` instead of `docusaurus`, but that shouldn't affect anything.
Figured it out...@16:54, just to the right of where you highlighted. "...in the folder set as app_location in the workflow file." For mkdocs, the app_location is /site. Had to move the staticwebapp.config.json into that directory. Now it works! Thank you again for making this video. All the other vids I watched were using React, Vue, etc. They were too complex. This was perfect.
@@DougDoesTech I have used the same json which you showed in your example. So it has the redirect tag but not sure why it is not redirecting to auth page.
@@DougDoesTech I was not pushing the staticwebapp.config.json file from the repo because the static content was part of a pipeline in Azure. So I was creating this JSON file from the command line and I forgot to escape the JSON due to which it was not reading the redirect code. Anyways thanks a lot it saved a lot of time after watching your video. :)
I rarely if ever comment a UA-cam video (unthankful ass). But I have to: This video made my deployment work on the first run including AAD (tenant specific) authentication! Thank you, very on point!
Your video help me a lot, even the official documentation confuses on how to configure SWA easily. You video did the trick. Thanks or creating this
I rarely post, but when I do, it's to say thanks. This helped a lot. Very clear.
Awesome video, Thanks!! Would definitely love seeing a B2C walkthrough.
thank you for the video, it's very helpful, good luck with future content.
yes it will be very great if we can see the B To C integration
I ran into all the same problems. The custom auth requirement definitely isn't straight forward. Thanks, Doug!
Great stuff :), happy to watch
Thanks, Doug. This really helped me. For some reason, the manifest.json linked in the index.html causes unintentional redirects whenever I try to add any type of authentication. I just removed it and that helped me for now. Weird how this doesn't come up in your example, making me think this could be something specific to my organizational tenant.
Please show us how to connect to AAD B2c please!
Thank you!
Bro, how many times do you have to sneeze 🤧? Jesus Christ 😭
Anyway, this was wonderful. Keep it up!!
Great video. i am also interested in the B to C config. I was hoping to be able to support AAD and a third party saml provider.
How do you ensure unique content for each logged in user? I think some real world example with more popular react framework such as nextjs or remixjs would help a lot.
God bless you 😁
Is it possible to test it on local? If not is going to be difficult to use in real scenarios. Maybe better use MSAL
Thanks for putting this video together. For some reason, the `staticwebapp.config.json` file isn't being respected. I pasted the same values you did from the MS Learn page, but there is no auth being enforced when I open the page, even in an incognito window. Do you have any thoughts on this one?
Hm...yeah. I just re-created the Azure Static Web App, upgraded to Standard plan, created the `staticwebapp.config.json` file, same issue. I can't get the route /* to work. The website loads with no auth prompt. I'm using `mkdocs` instead of `docusaurus`, but that shouldn't affect anything.
That’s weird, all I can think is the file is in the wrong directory or some how not getting deployed? Do you have a public git hub you can share?
Figured it out...@16:54, just to the right of where you highlighted. "...in the folder set as app_location in the workflow file." For mkdocs, the app_location is /site. Had to move the staticwebapp.config.json into that directory. Now it works! Thank you again for making this video. All the other vids I watched were using React, Vue, etc. They were too complex. This was perfect.
@@DougDoesTech yep, that was it!
I followed the same steps but it didn't ask for the password, rather it says 401 Unauthorized access when I open the Web app URL
You need to add the redirect code on 401
@@DougDoesTech I have used the same json which you showed in your example. So it has the redirect tag but not sure why it is not redirecting to auth page.
@@DougDoesTech Thanks for your help I found the issue. It was something else. :)
Nice! What was it?
@@DougDoesTech I was not pushing the staticwebapp.config.json file from the repo because the static content was part of a pipeline in Azure. So I was creating this JSON file from the command line and I forgot to escape the JSON due to which it was not reading the redirect code. Anyways thanks a lot it saved a lot of time after watching your video. :)