-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🥕⭐ [Enhancement]: Add authentication.provider synonyms. #2407
Comments
Introducing synonyms like EntraId and OAuth definitly provides flexibility, also it sounds more intuitive. Some Questions:
|
Deprecate? Yes. Remove? Probably not. @abhishekkumams
Typo corrected: |
Should |
I think |
Changes in the configuration file require several steps:
|
I'll have a look at implementing this, probably next week! |
Update
runtime.host.authentication.provider
with synonyms for future planning.Values
Tasks
application_name
compatibilityNone
Some Data API implementations don't require any security at all. There is no option for
None
, althoughStaticWebApp
handles this in most cases. The truth is, this is slightly more likeSimulator
except it behaves the opposite—Simulator
treats everything asauthenticated
butnone
will treat everything asanonymous
.EntraId
Azure Active Directory was renamed to Microsoft Entra Identity. We will retain the previous
AzureAd
moniker for backward compatibility, but it will be marked as deprecated in the documentation once this synonym is available.OAuth
Currently,
AzureAd
is just a simple OAuth implementation, and any custom JWT implementation can use it to handle claims. However, it’s far from ideal to make customers chooseAzureAd
orEntraId
when their underlying authentication technology is not from Microsoft. This also opens up a future direction should we need to handle special cases withEntraId
.The text was updated successfully, but these errors were encountered: