F5 BIG-IP Access Policy Manager (APM) vs. HMA

I think that the platform is well suited to many Remote Access VPN solutions, but I also think there is a lot of room for improvement on the backend. If you are hoping to deploy your APM solution across many different datacenters or colos, it may not be the best choice for the final solution.

Incentivized

• SAML 2.0 identity federation support.
• Integrates with third-party SSO solutions.
• Bridging modern authentication and authorization (SAML, OAuth/OIDC) and classic authentication and authorization methods.
• Policy routing

Incentivized

• There's some more advanced configurations within OAuth that I think could be fleshed out and easier to approach.
• There's a lot of things in F5 BIG-IP Access Policy Manager policies that I find myself recreating every policy. An easier way to copy objects from one to policy to another.

Incentivized

Integration with F5 BIG-IP systems that we plan to keep using for a while.

Incentivized

If F5 BIG-IP Access Policy Manager usability is fine it's not hard to use if you read the documentation but it does feel dated and could use a responsive design update to modernize user interface to current standards.

Incentivized

It is open platform so support is not good and than F5 and features visibility as not good as F5. F5 Set up and easy to use to admin console. Also have more feature visibility for load balancing, web server accelerator, application server ddos protection and WAF. F5 more efficient to handle concurrent request.

Incentivized

• Simplified our approach to company-wide VPN solutions greatly by allowing us to use a single product instead of multiple products like we had before
• Can handle 15000-20000 users at once with no issues
• Was able to configure to support users travelling with 4G connections on their laptops and accommodate constant changing IP addresses

Incentivized