Azure Static Webapps is not creating custom authentication

[RomanPanaget]

Describe the bug

Some well-known configurations are not correctly picked up for auth proxy creation.
Cannot provide it publicly, only in private, but it is a Keycloak OIDC config.

To Reproduce
Steps to reproduce the behavior:

1. Deploy the Azure SWA with staticwebapp.config.json like this:

{
  "routes": [
    {
      "route": "/*",
      "headers": {
        "Cache-Control": "no-store"
      }
    }
  ],
  "auth": {
    "identityProviders": {
      "customOpenIdConnectProviders": {
        "keycloak": {
          "registration": {
            "clientIdSettingName": "KEYCLOAK_CLIENT_ID",
            "clientCredential": {
              "clientSecretSettingName": "KEYCLOAK_CLIENT_SECRET"
            },
            "openIdConnectConfiguration": {
              "wellKnownOpenIdConfiguration": "<private keycloak valid well-known URL>"
            }
          },
          "login": {
            "nameClaimType": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name",
            "scopes": ["openid", "profile", "email"],
            "loginParameterNames": []
          }
        }
      }
    }
  },
  "globalHeaders": {
    "Access-Control-Allow-Origin": "*",
    "Access-Control-Allow-Methods": "GET, POST, PUT"
  }
}

KEYCLOAK_CLIENT_ID and KEYCLOAK_CLIENT_SECRET are correctly set up in Application Settings.
3. Wait for deploy to finish
4. Navigate to .auth/login/keycloak and see a 404 code

Expected behavior
Expected to see at least a login page from my keycloak provider

Screenshots
From diagnostics:

Additional context and possible hints
If I specify the separated auth, token, certs, issuer URLs, I can get a login page but the flows seems buggy and I can't get logged in in the end

I can provide my SWA URL, tenant and well-known URL for further details in DM

Thank you

[RomanPanaget]

@mkarmark is there any logs on your side we can check together during the deployment ? Please reach out to me

[eferfolja]

Having the same issue as described above on two SWA using Custom Auth. One uses Azure B2C, the other one uses a custom config for Google. Both apps were working for months.

[4ux-nbIx]

Any update on this? I'm facing the same issue... And today I can't even deploy a new Static Web App via anything!!! Getting 500 in both Azure Portal and az-cli :(

[manoj271106]

same error here , azure b2c auth integration doesn't seem to be working, I get a 401 error once the flow redirects or the callback happens.

[vtapadia]

Probably a very old issue, but I also did the configuration and getting the same 404 error.

Any pointers on what is wrong here... :(