mspbizguy•

This! It's insanely insecure to not have 2FA in LabTech and simply insane that the only option they have is not only over-complicated garbage, it's owned by Kaseya. Word I heard from CW is that other Auth methods aren't even on the road map. They suggested trying a third party Duo plugin that they haven't even tested. So many of us would fail a compliance audit because of this. It's shocking and disappointing that they don't take security seriously. How can our clients trust us if our own software vendors don't support standard security practices. As it is, we can't tell if someone tries to brute force, and I'm pretty sure there isn't a way to enforce strong passwords. Wtf LabTech?

5
wogmailOP•

Definitely fill out the form requesting a feature enhancement if you haven't already. Link is in the post mentioned, but here it is

https://cp.labtechsoftware.com/#/forms-library/enhancements

2
drinkxon•

Just submitted an enhancement request for Google 2FA/Labtech support.

2
theclevernerd•

Submitted feedback earlier today.

Hopefully this gains enough traction and it is implemented just like it is in ScreenConnect and CW.

2
mspbizguy•

Done. Hopefully they will work it into the current release, 11 looks pretty awful. We may be moving off LT anyway, those tiles look like they were designed 5 years ago. Such a productivity drain.

1
ninjaspy123•

If you want pseudo 2 factor and you're hosted on prem, there is a method to disable control center logins unless you're hitting the local address of the server. This forces your guys to be on a VPN, which acts as a 2nd auth point.

I'll look how the doc if anyone is interested, just on mobile right now.

2
limp15000•

I was suggesting this last week in the mean time. I'd be interested in your doc ;)

2
wogmailOP•

Yeah, I'd be interested in knowing how to turn that on.

1