We’ve recently picked up this work again and apologize for the lack of updates.
The approach we previously pursued did not work well and we’re re-pivoting to a different solution that will enable custom domains to be easier to set up and manage.
We hope to have this ready for a public preview late-2020 or early-2021.
At the moment our recommended method for checking the identity of the current user is to check several attributes added to incoming requests. This is to allow your application to go completely in and out of memory on lower priced tiers without “always-on.” Check out the tutorial below for the header names.
We would like to have language specific auth functionality like this in the future. I am placing this item in “unplanned” to be used in future planning sessions.
thanks for your feedback!
Azure App Service Team
An error occurred while saving the commentBrett Styles commented
It really limits the usefulness of the API if a REST endpoint gives all users the same access rights and scope. The scenario where it returns data specific to the logged in user or group (user v admin etc) currently means two API apps one Admin and one user exposing the same REST endpoint.
The gateway already intercepts the request to validate the token when accessing the endpoint so handing that token on to the WebApi to run an OAuth2 authorize cycle to the gateway would at least give us a way to access the claims principal.