OAuth pre-authentication in Azure Application Proxy
Currently pre-authentication in Azure Application Proxy implies user interacive logon to Azure AD. It would be great if one could choose an option to pre-authenticate as a annplication with a token in the same Azure AD tenant (and select an Oauth app which is regitered in the same tenant).
That's very useful when there is an external application/server accessing on-prem app via Azure Appliation Proxy would pre-authenticate with OAuth in Azure AD first and pass this token AAP.

Thanks for sharing your feedback. We will be further reviewing this feature and will update soon when we have more details.
4 comments
-
yang commented
WOW, 71 votes and more than 1 year.
How efficient the Azure AD group team is!!!
Let's make votes to 1000
-
Anonymous commented
I've noticed that if you add your own secret to the registered app that is created along with the application proxy, you can generate an access token (using client_credentials) however it does not issue AzureAppProxyAccessCookie, and without this cookie each request takes 4 to 5 seconds to complete.
Along with oAuth preauth, please allow for this cookie to be given in response to the client_credential grant_type.
-
Morten commented
This has been under review for more than 1 year, would it not be about time with an update?
-
Leo D'Arcy commented
This is mostly doable using the instructions found https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-configure-native-client-application. I've hit some issues with it which I have raised a seperate UserVoice Item at https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/38013307-enable-dedicated-app-proxy-authentication-header.