![]() Now it should work, with ADAL giving you perfect SSO from your Office applications. To do this you need to run the following PowerShell cmdlet and restart the ADFS service on all servers in the farm.Įnable-AdfsEndpoint -TargetAddressPath "/adfs/services/trust/13/windowstransport" To fix this, you need to enable an ADFS endpoint that is disabled by default. It should support Integrate Widows Authentication for WS-Trust 1.3.’, additionalInformation=’Authority: If you enable the TCOTrace registry key, the %temp%\ logfile is created and here I found the following entry:ĪDAL: message=’Could not discover endpoint for Integrate Windows Authentication. I contacted the Microsoft product group and verified that this was indeed supposed to work and was one of the primary use cases. However, despite of using ADFS and having the adfs website added as an “intranett site” in security settings in IE, all I got was forms based authentication and not single sign-on as I expected. I followed the guidance and enabled ADAL. ![]() ![]() With ADAL, the Office applications support “Modern Authentication” which means web redirects instead of using the old basic authentication and “proxying credentials” through Office 365. I am currently testing out Office 2013 with ADAL which is currently in preview.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |