A question about Password Hash Syncronisation (PHS) and single signon to an Azure App

Copper Contributor



Can someone please clarify the following for me,


if I have on-premise AD and AD Connect to sync both the user account and their passwords from on-premise to Azure AD (so the same UPN and password exists at both locations)


Next I have an Azure App and give the user rights to run the app via the Azure MyApps


when the user on premise goes to access the application in Azure (remember No AD FS), I assume the user will be asked to login to Azure AD (all be it the users name and password will be the same as on-premise)


My questions are


1:) if the user is asked to login when accessing the Azure app, is there a way to 'save' this (in a cookie or similar) so the next time the user opens the app it logs straight in with  no intervention required from the user  ?


2:) I realize Windows uses Kerberos tickets and turns the PAC in these Kerberos tickets into Windows Tokens (to access securable objects), and Azure using Azure SAML, JWT, OAuth2 and OpenID connect

So different set of protocols, but on a Windows internal network you can use 'pass thought authentication' whereby if your username and password it the same (NTLM protocol etc.) you can simply login to the resource you want to access.

Can a similar thing be done when accessing an Azure hosted App from a Windows AD Domain, e.g. rather than remember the username and password once entered once (as in 1 above) simply pass it through and if it matched the one stored in Azure AD, automatically get an Azure token and access the app with no user prompt




0 Replies