WatchGuard AuthPoint First Implementation Review
Anonymous | TrustRadius Reviewer
December 10, 2019

WatchGuard AuthPoint First Implementation Review

Score 8 out of 10
Vetted Review
Review Source

Overall Satisfaction with WatchGuard AuthPoint

We were in the process of implementing WatchGuard AuthPoint to one of our clients after internal testing. The implementation with that client was put on hold after issues with Office 365 were encountered immediately following implementation. It is still in use for my personal testing environment for Office 365 and Windows Login MFA.
  • MFA for Office 365 **Without shared mailboxes and calendars**
  • MFA for Windows logon
  • The initial portal setup for MSPs is cumbersome and not well documented.
  • There are issues with Office 365 integration, specifically shared calendars and mailboxes.
  • Objective 1: Protect Office 365: ROI is negative -- spent too many hours troubleshooting issues and ended up removing from the client's O365 Tenant.
  • Objective 2: Protect Windows Logon -- ROI is good here. Easy setup and configuration. Functions as desired.
Duo seems to work better for the Office 365 environments than AuthPoint. So far we do not have calendar and mailbox sharing issues with Duo. We have not fully deployed to a client site yet, but plan to this month. Duo also provides MFA protection for Windows Logon and SSL VPN via RADIUS which will provide our clients with one product for all three protections. This is very important to me because I want to simplify the MFA experience for our clients as much as possible.
This is partially true. There is a gateway service that runs on a server in the client's environment, but that is software-based not hardware-based. This creates an issue if the gateway service is running on an on-premises server and Internet or power is lost, because users will not be able to log into the Office 365 portal. In this configuration, WatchGuard AuthPoint is not fully a cloud service as it relies on the availability of the gateway service running on the client's network.
The process of setting up the AuthPoint app on smartphones was fairly simple and user-friendly instructions were provided. The users we were working with did not seem to have any issues with this part of the setup.
SSO capability is a nice feature for our cilents. The site we were planning on deploying AuthPoint to already had SSO enabled for the services we were trying to protect with AuthPoint. If they were using other SAML based applications, I do believe this would have been a benefit to the end users.
Support from WatchGuard for the AuthPoint product has left me feeling that they are not overly familiar with the product themselves. I had some issues with federation with Office 365 initially, which took weeks to find a resolution for and the support team did not fully solve the problem so much as provide me with a little more information, which I used to get the problem resolved. I've had a ticket open with them for a couple of weeks now for Office 365 calendar and mailbox sharing after AuthPoint implementation that has yet to be resolved.

Do you think WatchGuard AuthPoint delivers good value for the price?

Not sure

Are you happy with WatchGuard AuthPoint's feature set?

Yes

Did WatchGuard AuthPoint live up to sales and marketing promises?

No

Did implementation of WatchGuard AuthPoint go as expected?

No

Would you buy WatchGuard AuthPoint again?

Yes

Based on my experience with WatchGuard AuthPoint, it is best suited for Office365 scenarios where calendar and mailbox sharing is not present. It functions well for Windows Logon and SSL VPN protections. I have not tested with other SAML based applications yet, so I cannot speak to its functionality there.