Static-web-apps: Auth Bug - SSO with sign up link.

[ShanonJackson]

Let me know if you can't reproduce, love the static-web-apps offering and i'm basically frothing at the mouth to start using it in production (please deliver azure dev ops support 👍 haha)

Admin: Generates "Role management" invite link for AAD.
Admin: Pastes user his invite link.
User1: Is already signed into this AAD on another tab, when he clicks invite link he gets 401 unauthorized INSTEAD of a sign up/sign in form.

I believe this occurs because he technically is signed in; however has not granted access to the application. This can easily be solved by opening the sign up link in incognito and works as expected.

related files: (routes.json)

{
  "routes": [
    {
        "route": "/",
        "allowedRoles": ["super_admin"]
    }
  ],
    "platformErrorOverrides": [
        {
          "errorType": "NotFound",
          "serve": "/404.html"
        },
        {
          "errorType": "Unauthenticated",
          "statusCode": "302",
          "serve": "/.auth/login/aad"
        }
  ]
}

[mkarmark]

Hi @ShanonJackson,

Thanks for bringing this to our attention! Looking through the logs and doing a little searching it seems that this is something we need to look deeper into. We'll get back to you here when we have more info on the fix for this issue.

[ShanonJackson]

Any ideas when azure static web apps will start looking for a production release? really interested in leveraging it for our team (i know this isnt the time or place) but couldn't find any info about possible release date online.

[craigshoemaker]

Just wanted to note here that the _routes.json_ file is deprecated. Routes, overrides and general configuration of a Azure Static Web Apps are now powered by the staticwebapp.config.json file.