Unable to sign in at work on Kubuntu LTS 18.04

Question

Unable to click the submit button when trying to sign in as my workplace uses SSO.

Answer 1

I had a similar problem, but clicking on "submit" brought up a request to open my Gnome keyring. I have been using KDE for years, and didn't remember a password to that keyring. I ended up going into "~/.gnome2/keyrings" and mv'ing the existing *.keyring and *.keystore files out of that directory. At that point, I got a request that an app wanted to create a new keyring entry, and I allowed it. That got my login to actually continue.

I'm not sure why it wanted to put my login/password in a keyring (if that's what it was doing), but getting rid of my old keyring files allowed me to move forward. There might just be a pop-up that popped under requesting a keyring unlock - and if you know the password, that might get you moving again. Cheers. [AER]

Answer 2

I had a similar issue on OpenSuSE Tumbleweed. On one PC all works fine, on the second the submit button did not do anything. I discovered that the 'gnome-keyring' package was not installed. After installing it via Yast/zypper everything works fine.

@MicrosoftThe rpm for teams should check dependecies when installing, please fix this.

Answer 3

I experienced the same issue due to a faulty proxy setting (found via wireshark).

For me, MS Teams picks up the KDE Proxy settings when running in a KDE environment (which makes sense but still is somehow an exception).
Change it in System Settings/Network/Settings/Proxy

It seems, MS Teams also accepts the chromium-style cmd-line options, like --proxy-auto-detect, --proxy-pac-url=URL, --no-proxy-server and --proxy-server=host:port

If the above did not work and you use a Kerberos enabled Linux machine the following might lead to success:
First, check if you have a TGT using klist command
Second, you probably need to start MS Teams with the cmd-line option --auth-server-whitelist=.example.com

In our company, I can not use a fixed proxy setting since the proxy can not access the ADFS server - thus I need to use the proxy auto configuration or a combination of --proxy-server=host:port and --proxy-bypass-list=*.example.com

Answer 4

Simmilar issue here. the Teams client requests credentials to authenticate against the ADFS-Server. The ADFS does not accept the credentials and responds with "username/password incorrect".
Looks like an issue with WindowsIntegratedAuthentication and the chromium engine.

Answer 5

Same issue here on Arch/Manajro with xfce. It was caused by missing gnome-keyring. Once I installed it, it worked:

pacman -S gnome-keyring