2017-4-22 Skype for Business; April 22, 2017. Solved There was a problem verifying the certificate from the server for SFB 2015 Solved There was a problem verifying the certificate from the server for SFB 2015. Save my name, email, and website in this browser for the next time I comment. This site uses Akismet to reduce spam. Learn how your. You are an Office 365 subscriber and trying to launch the Lync or Skype for Business client application. When attempting to login you receive the following error This happens due to server authentication failure. But you can set the server settings manually. 2020-5-28 For the best Mac client experiences and an always up-to-date infrastructure, we recommend all customers migrate to Office 365. Skype for Business Server 2015 customers should at a minimum download and install the Skype for Business Server 2015 Cumulative Update version 9319.272 or higher. Jul 25, 2017 Time to roll up my Mirazon sleeves and dig in. First things first, I pulled some client logs and looked at what was going on in the background. Here’s the first thing I saw in the UccApilog: Well, admittedly, that was a new one for me. I’d never seen an issue with Skype for Business Online provisioning a certificate before.
Requesting and assigning a certificate to Lync/Skype for Business server is a crucial process. Any kind of ignorance while requesting the certificate can trouble It simply means that the root certificate of certification authority does not exist on the local server from where the request is being generated.
Recently we got some support request tickets regarding MAC clients which weren’t able to sign-in into Lync because they were missing the necessary root CA certificates.
Those root CA certificates are required in order to sign-in into Lync rather it’s on the internal or external network.
the following guide was written by a colleague of mine, Lior Gilboa and it explain how to install a root CA certificate on a MAC client:
Related Posts
I've been having this issue for quite some time as well, and have been working with a Microsoft Skype for Business (SfB) support engineer on it. To be certain it's the same, or similar-enough issue, here's the setup I've been working with (or against it seems):
* Skype for Business 2016 (any version, including latest in the insider 'Fast Ring' releases)
* Macbook Pro - Early 2011
![]() Date Time Calendar
* OS X 'El Capitan' - v10.11.6
* Corporate domain is on Azure AD (Active Directory)
Mac Skype For Business Certificate Error
* When signing in with the AD account, you are either a) Given a choice between 'Work or school account' or 'Personal account), b) usually automatically redirected to the company branded signon page.
If that matches up, the next step is to check the certificate which is on domain's federation services (ADFS) host. This may require getting IT involved to find it, or reviewing the SfB logs.
When you get the host name, for example, 'adfs.mycompany.com', go to that address via HTTPS in Safari. So you'd go to 'https://adfs.mycompany.com'. Once there, click on the lock to the left of the address in the address bar and click the 'Show Certificate' button. Make sure that the selected certificate, in the tree view at the top, is the bottom-most one. The bottom pane should show some brief certificate info (Issued by, Expires, 'This certificate is valid' type message, etc.). Expand the 'Details' section in that lower pane, and look for the 'Signature Algorithm' line, which should be, roughly, the 12th one down. If on that line, you have something similar to 'SHA-512 with RSA Encryption' (forget about the long number afterward), then that is the source of the issue with logging on, and also, activating Office 365 (if you have a company account for it).
OS X prior to 10.12 (Sierra) does not *natively* support 512 bit certificate signatures. So while browsers and everything else shows that, yes, the certificate is good, valid, unexpired, etc, the low level network stack in OSX, which is used by SfB to initially connect, does not, so it cannot validate that the certificate is valid, thus causing this issue.
Unfortunately, at this time, there doesn't appear to be a way to wedge in support for 512 algorithms in OSX, and that includes forcibly upgrading/linking openssl. The only way I've found to date, to use SfB on anything less than 10.12.x, is to essentially MITM yourself, using a proxy application, such as Charles, which will create its own fake certificate which you must trust, to connect.
Skype For Business Certificate Error Mac
I apologize for such a long writeup, but given that despite my hours and hours and hours spent over months of researching the issue, I hope to provide as much useful and helpful information as possible for any future Googlers/Bingers/DuckDuckGoers/etc.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |