WatchGuard AuthPoint Review
Overall Satisfaction with WatchGuard AuthPoint
We use it internally and also deploy it to our clients. One of the problems we are facing currently is that Carbon Black blocks the software because of the fact that it uses PowerShell Script to generate geo-coordinate data back to WatchGuard AuthPoint. I've been liaising with WatchGuard support for help on this issue, but no luck so far.
- Simplicity to setup
- Easy implementation
- No fuss setup with software token
- Azure AD sync works well
- Support
- App sometimes takes longer for it to boot
- Change the way it sends out geo-coordinate (Not using PowerShell)
- More revenue
Mainly because of the issue with the way it sends out geo-coordinate using PowerShell. We want to try out other similar software to see if it's doing the same.
We use AzureAD to sync users, so that eliminates the need to deploy a gateway server in-house. This is particularly good for clients with no servers in their environment.
Users are generally happy with the app. Some are quite happy that they can approve the sign-in using a smartwatch as well.
To be honest, it's easier to implement MS 365 SSO to third-party applications than using WatchGuard AuthPoint. I am not saying WatchGuard AuthPoint is not good, but user normally remembers their email passwords, so it makes it easier to implement it using MS 365 SSO and combine it with the native MS 365 MFA.
Do you think WatchGuard AuthPoint delivers good value for the price?
Yes
Are you happy with WatchGuard AuthPoint's feature set?
Yes
Did WatchGuard AuthPoint live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of WatchGuard AuthPoint go as expected?
Yes
Would you buy WatchGuard AuthPoint again?
Yes