We have SharePoint 2013 on premises with all of the latest patches/roll ups. We have configured SharePoint to use Kerberos authentication (as we would like to upgrade from Microsoft TMG to Microsoft Web Application Proxy). We cannot open SharePoint libraries either externally (going through Web Application Proxy) or internally (hitting SharePoint servers directly) using certain applications. We can open SharePoint libraries using the following:.

Browsers - Any browser on any device. This works both internally and going through Web Application Proxy/ADFS. Windows Explorer. Thanks for the suggestions Winnie. Unfortunately, we have tried the suggestions already and were still unable to get authentication to work properly. I believe this may be a bug with the Microsoft Office Modern Authentication mechanism and Kerberos authentication on Mac and mobile devices. I know of two separate organizations having the exact same issues and SharePoint and Kerberos are configured using Microsoft's own guides and documentation by two separate Microsoft Gold Partners.

Again, authentication works properly when accessing SharePoint via browsers or Win32 applications. It even works on the Microsoft mobile versions of Office (although the method that the win32 apps use to access SharePoint is not 'Modern Authentication').

One thing to note is that the 'Add a place' option in Win32 Office apps only allows SharePoint Online using Modern Authentication. You must browse to an on-premises site using a file browser window instead of the Modern Authentication window. Hi Tim, We worked with Microsoft for two months on this and in the end, they concluded that there was a limitation in the clients and in Mac and the behavior was expected. We also tried using Azure Web Proxy and Azure AD Connect passthrough authentication to get around the Web application proxy and ADFS completely with no luck. At this point, we're still investigating a solution (as we need to dump TMG) and have had some mixed success with using F5 iRules but it gets complicated. We considered looking into Sophos UTM as well. Wish you the best of luck!

Amaya-8.6: Gdk_imlib.h: Incorrect Search Method For Macbook Pro

Here's the final response I received from Microsoft regarding this issue: ' Hi Dean, After further investigation found out this is a limitation on MFA OSX, does not support windows integration authentication, Mac client it notes that device-based policy support is planned for the future s, it will won’t work with Mac clients as of now. If you plan to move from ADFS over to using AAD conditional access, the Mac Outlook 2016 will eventually work (planned for the future) but currently will not work. Office 365 SharePoint Online Mac OS X Office 2016 apps and Microsoft Teams OS X app for multi-factor authentication and location only; device-based policy support planned for the future. This behavior for Outlook 2016 for Mac is by design.

Outlook 2016 for Mac has Modern Authentication enabled by default. Other customers have run into this same behavior. A Design Change Request was submitted this month to the Product Group. The request was rejected, there is a workaround that can be applied to your corporate owned Macs to disable Modern Authentication in Outlook. The client build must be at least v15.30 for the workaround to apply.

I recommend testing this workaround on one Mac then verify it will accomplish you desired results before rolling to additional Macs. Here are the steps to apply the workaround:. Quit Outlook. Open Terminal using one of the following methods:.

With Finder as the selected application, on the Go menu click Utilities, and then double-click Terminal. In Spotlight Search, type Terminal, and then double-click Terminal from the search results.

Enter the following command in the Terminal window, and then press Enter. Defaults write com.microsoft.Outlook DisableModernAuth -bool YES. On the Terminal menu, click Quit Terminal.

Unfortunately, this workaround is not valid for non-company owned Macs (i.e. Personal Macs purchased by the end users). As of now, the Product Group is working on the rejection letter for the DCR which will have details of the reasoning.' I have this same problem using MSOffice 2016 on company macbook pro, and connecting to sharepoint. Whenever my domain password changes I get the errors described at top of this chain. Here's my fix on Mac: 1. Copy the sharepoint URL of your internal company site.

Go to that location in Safari on your mac. For the one note location they give a url like onenote:so I took off the onenote: prefix and went to the Url. Potentially you can knock off some of the end of the url to go to the main sharepoint project location. It will ask you to sign in - do so with your company login. Then I navigated down to where my actual one note notebook was in the sharepoint site through safari. Click on one of the docs or sites you're trying to access in safari. Mac will popup something asking to modify your keychain - you type in authorization which must be the pwd you use to login to your mac.

Amaya-8.6: Gdk_imlib.h: Incorrect Search Method For Mac Download

Now things work fine. Until my pwd changes again.