Posted on 08-30-2017 06:31 AM
I have a https SharePoint 2016 on premise site collection. Below are the functionalities implemented in the site collection. 1. SharePoint hosted apps are deployed. For example- SharePoint domain is contoso.com and the app domain is contosoapps.com 2. Because of continous app authentication, I have created a seperate site collection in the name of app domain (https://contosoapps.com) and added https://*.contosoapps.com in the Local Intranet zone. 3. Two wildcard certificates (.contoso.com and .contosoapps.com) were purchased and they being used for site collection and for other site collection created in the name of app domain.
Scenario 1: When site is browsed from servers in domain, the site collection works fine and SharePoint hosted app works without any authentication prompt in all browsers like IE, Chrome, Firefox and Safari.
Scenario 2: When vpn is connected to the domain from Mac and site is browsed, SharePoint hosted apps are asking for credentials (credential prompt for each and every app in the page) in all browsers.
Can anyone help/advice me on this issue?
Posted on 08-30-2017 10:01 AM
@naveenprasath Sounds like it could be Kerberos related. We had a similar issue that was affecting our users and it was due to the kerberos account that Sharepoint was using was not properly configured.
Posted on 09-05-2017 09:32 AM
Hi, Thanks for your response. Could you please point me where the configuration of Kerberos might be the problem or else let me know the details of the area so that I could provide you the same and correct it. This will help troubleshoot and solve issue faster.
Posted on 09-05-2017 09:37 AM
@naveenprasath Unfortunately I cant provide mush more detail than that. I was working with our Sharepoint expert here. You can look at the ticket viewer app and use the command-I to see more detail. Thats where we saw the invalid tickets.
Posted on 09-05-2017 09:39 AM
@naveenprasath In Sharepoint speak, you need to enable "Claims Based Authentication", i know that much but the rest was dealt with by the Sharepoint team.
Posted on 09-06-2017 11:04 PM
@RogerH Thanks for the response. We will check it and let you know.