The SSRS installation & configurations are the same on both versions of Windows Server 2012 & 2016. 16384, we are able to log in to the report server with Safari as expected without issue. Windows Server 2012 R2 Standard ( Build 9600) with When repeating the same SSL scenario described above with SQL Server Reporting Services 2016 (build 13.0.442) installed on We’ve also tried adding basic in addition to NTLM which resulted in no change. All installs of SSRS in the above mention servers are using the same NTLM setting in the nfig file (see below). The Safari browser has no issue browsing to a plain IIS site using the same certificate, but fails on the report server so I don’t believe this is an IIS issue alone. When browsing the non-secure URL with Safari ( the login dialog appears as expected, accepts the credentials, and then continues to the report server. There are no event logs, SSRS logs or IIS logs generated that I can find. Will never proceed to the report server site (see attached). The credentials then seem to be accepted, but then the credential dialog appears again, over and over and Is set to always trusted and added to the certificates login area of Keychain Access (equivalent of adding a trusted site in Internet Explorer). When attempting to browse the SSRS secure URL with Safari ( the login dialog appears, indicates that the certificate is not trusted. The SSL certificate is issued from an internal domain Certificate Authority. Windows Server 2016 Standard (3 Build 14394) with We have run across an issue with SQL Server Reporting Services 2016 (build 13.0.442), SSL and the Safari browser on a Macbook, all running in a domain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |