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

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

I can't think of anywhere this would be good.

• 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

Once things are set up, it is nice and easy to get the Edge Client running on user's PCs. However, that setup process can be a bit daunting at first using the Policy Manager, and reviewing session logs can be difficult at first if you aren't 100% sure of what you're looking for.

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

In my opinion, it's probably the worst product of it's kind, but I honestly don't know.

• Single sign on is great for students and faculty and staff
• Users don't have to log in multiple times
• Users don't need to remember multiple login IDs and passwords
• Multi Domain SSO support bridges many internal and external facing products with single sign on

Incentivized