Finally I got it running with adding our root CA cert with certutil
certutil -A -n "ROOT-CA" -t "TCu,Cu,Tu" -i /usr/share/ca-certificates/ROOT-CA.crt -d sql:/home/${USER}/.pki/nssdb
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I'm using the Teams Client for Linux on a Ubuntu 18.04 LTS behind a corporate proxy.
This is what I get, when trying to login:
desktop-987c88d0-fece-4708-bd29-f87333f90db9
Error code - -202 ERR_CERT_AUTHORITY_INVALID
Failed to load: https://
I guess that this has something to do with the redirect to the corporate login page and the certificate that is used there. Any idea how to check the cert store of the teams client? Or how to fix this behaviour?
-
Daniel
Finally I got it running with adding our root CA cert with certutil
certutil -A -n "ROOT-CA" -t "TCu,Cu,Tu" -i /usr/share/ca-certificates/ROOT-CA.crt -d sql:/home/${USER}/.pki/nssdb
Hi Daniel!
Does anyone else have the same issue?
In my experience, Teams for Linux client don't need to install certificate. In our test environment(Ubuntu 18.04), we installed the Teams for Linux and didn't install certificate. It works well. So we think this issue may related to corporate proxy certificate. We recommend you check if your corporate certificate is trusted or expired. For more details about this issue, you can refer to:
https://www.guildcafe.com/fix-net-err_cert_authority_invalid-error.html
Hi,
I'm working on a linux (ubuntu) machine. I have the exact same problem.
I've already tried the followings:
-We have MITM decrypt for https, so internal ca have been added to the cert store of the system.
-With wget I checked that the url from the log works well.
Error log of Teams:
Mon Nov 23 2020 11:24:56 GMT+0100 (Central European Standard Time) <7906> -- event -- name: desktop_navigation_provisional_load_failed, errorCode: -202, errorUrl: https://teams.microsoft.com, message: ERR_CERT_AUTHORITY_INVALID, vdiMode: 0, eventpdclevel: 3,
Mon Nov 23 2020 11:24:56 GMT+0100 (Central European Standard Time) <7906> -- error -- Page failed to load with error code -202: ERR_CERT_AUTHORITY_INVALID: https://teams.microsoft.com
Mon Nov 23 2020 11:24:56 GMT+0100 (Central European Standard Time) <7906> -- warning -- Page failed to load with unhandled error code -202: ERR_CERT_AUTHORITY_INVALID: https://teams.microsoft.com
Wget output:
juhaszis@DSOL-0012N:~$ wget -d https://teams.microsoft.com
DEBUG output created by Wget 1.20.3 on linux-gnu.
Reading HSTS entries from /home/juhaszis/.wget-hsts
URI encoding = ‘UTF-8’
Converted file name 'index.html' (UTF-8) -> 'index.html' (UTF-8)
--2020-11-23 11:26:29-- https://teams.microsoft.com/
Resolving teams.microsoft.com (teams.microsoft.com)... 52.113.194.132, 2620:1ec:42::132
Caching teams.microsoft.com => 52.113.194.132 2620:1ec:42::132
Connecting to teams.microsoft.com (teams.microsoft.com)|52.113.194.132|:443... connected.
Created socket 3.
Releasing 0x000055b94eb4f6f0 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 3 to SSL handle 0x000055b94eb4f820
certificate:
subject: CN=teams.microsoft.com
issuer: CN=NL_InternalCA,O=Netlock Kft.,L=Budapest,ST=Budapest,C=hu
X509 certificate successfully verified and matches host teams.microsoft.com
---request begin---
GET / HTTP/1.1
Does teams use same internal cert store instead of the OS store on linux?
Do you have some workaround?
István