App Service uses federated identity, in which a third-party identity provider manages the user identities and authentication flow for you. Five identity providers are available by default. The documentation states that you can also integrate another identity provider.
The App Service documentation on authentication and authorization, here: https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization states that besides the Identity providers which are pre-configured, such as Azure AAD, Microsoft Account, Facebook, Twitter etc. citation "You can also integrate another identity provider".
I haven't found any documentation on how to actually do that. I would like to look at some IDaaS, such as Okta, or even provide our own Identity-Solution, for example using a setup of gluu server.
I am researching more information on this. In fact, I would like to not use Azure AD B2C or B2B because both licensing models are not perfect for us. While B2B will force us to license a lot of Azure AD licenses (one for every 5 external Identities), B2C actually charges for more or less every interaction with the ID Service that it provides.
Thoughts on this welcome!
Tim
# It may be possible that code needs to be written,
# but I sincerely hope to get by with simple or even not so simple
# configuration
# If code needs to be written, that would also be an option.
I would hope to get a comprehensive example of a foreign IDaaS which has been configured inside an App Service and is used to authenticate users.
