F5 BIG-IP Access Policy Manager for COTS applications protection
Overall Satisfaction with F5 BIG-IP Access Policy Manager (APM)
Protecting applications before exposing them to the Internet. Often COTS applications.
Pros
- Using OAuth with a COTS app that does not support it.
- Integrated with different authentication systems.
Cons
- JWT tokens process DIES.
- UI is cumbersome.
- Replicating configuration to another F5 cluster is time consuming.
- Again, works well for protecting COTS applications that don't integrate with other corporate solutions
- F5 BIG-IP, F5 BIG-IP DNS, F5 BIG-IP Local Traffic Manager (LTM) and F5 BIG-IQ Centralized Management
Do you think F5 BIG-IP Access Policy Manager (APM) delivers good value for the price?
No
Are you happy with F5 BIG-IP Access Policy Manager (APM)'s feature set?
Yes
Did F5 BIG-IP Access Policy Manager (APM) live up to sales and marketing promises?
No
Did implementation of F5 BIG-IP Access Policy Manager (APM) go as expected?
No
Would you buy F5 BIG-IP Access Policy Manager (APM) again?
Yes
F5 BIG-IP Access Policy Manager (APM) Feature Ratings
Using F5 BIG-IP Access Policy Manager (APM)
5 - Administrators. Thousands of clients go through the F5 BIG-IP Access Policy Manager apps.
5 - Same team does BIG-IP LTM and DNS administration.
- Protect COTS applications
- Handle authentication for other apps that don't yet do it themselves
- Protecting BigIPReport
- Moving from LDAP probably to AD cloud for authorization
Evaluating F5 BIG-IP Access Policy Manager (APM) and Competitors
Yes - Oracle WAM gateway
- Integration with Other Systems
We considered using Open Source solutions and I expect we'll revisit that option.
Using F5 BIG-IP Access Policy Manager (APM)
| Pros | Cons |
|---|---|
Well integrated Consistent Feel confident using | Do not like to use Unnecessarily complex Difficult to use Requires technical support Slow to learn Cumbersome Lots to learn |
- Replicating config to other data centers is difficult
- Many error messages in the logs are unclear
- JWT renewal process DIES and does not log that it dies
- Killing active sessions is difficult as it's not easy to find the correct session

Comments
Please log in to join the conversation