Static-web-apps: Support a custom user store for identity

[adamjcooper]

Congrats on the beta release.

At the moment it looks like you have built-in support for some popular third-party auth providers, where users already have an account with the third party. What is the story if I want my users to be able to sign up for an account on my site directly? That is, how would I go about offering people a way to sign up for an account for my own domain rather than using an existing Facebook, Google, Twitter, GitHub, Azure AD, etc. account?

Thanks!

[mkarmark]

Thank you for using Azure Static Web Apps!

For preview, using the five offered providers and having the users log in to Azure Static Web Apps is the only option for authentication/authorization.

Supporting custom authentication is something we plan to offer in the future.

Thank you for your feedback. Keep them coming.

[anthonychu]

We don't currently have plans to directly support authenticating against a custom user store that we provide. However, we may provide Open ID Connect support in the future and it might be possible to use a provider that supports a user store like Auth0 and Azure AAD B2C.

[DjolePetrovic]

So this blog post you wrote does not apply to azure static web apps? Or it does?

[anthonychu]

@DjolePetrovic That's correct. For the time being, OIDC integration is only available in App Service and Azure Functions.

[jpatdu-credovita]

+1 on OIDC integration for Azure Static Web Apps; this is the only thing missing for me to practically host all of my full stack web apps on ASWA.

[anthonychu]

We’re working on OpenID Connect support. No ETA yet but check back in a couple of months for updates.