Cloud Platform Release v24.9.1

We are pleased to release version 24.9.1 of our cloud platform that introduces a couple new features and fixes a few of bugs. Below are the details.

• Single Sign-on (SSO) support for Okta: A long awaited enterprise request to allow integration with Okta IDP is finally here. We’ve offered 2FA using email, SMS, DUO and a variety of TOTP apps for quite some time, but this is the first Single Sign-on integration, and we’re happy to announce that Okta is where we started. Integration with other SSO platforms will be here in 2025. For more information on where to find this feature and how to integrate it, please visit the Setting up Single Sign-on (SSO) with Okta Knowledge Base article.
  
  
• ANAME Duplicate Bug: Our prior release included the highly requested ANAME functionality, and in this update we corrected a small bug that would result in duplicate IP addresses in very specific situations.
  
  
• Network ACL Updating: We released a number of improvements to the Network Access Control List (ACL) update process on the back-end. These improvements considerably speed up ACL deployment, especially for large lists.
  
  
• Edit HTTP Monitor Bug: If a HTTP monitor was configured with very specific parameters during the initial creation, modifying it would cause an error. This has been corrected in this release.
  
  
• Networking Widgets: We added new widgets to the dashboard for networking that now indicate how many Caching and Compression policies have been created and deployed.
  
  
• Networking Geo Weighting Improvement: We vastly improved the speed with which Networking GEO Weight changes are updated across the platform. Previously a simple GEO weight change could take up to 2 minutes, but with this latest update it completes in a matter of seconds.
  
  
• Allow Unspecified URL: We added a new feature in the WAF/WAAP policy for Allow Only URLs to now Allow Unspecified URLs after one match. This will allow users to enter the application with an approved URL, and then traverse other URLs not specified as a result of the first match making it easier to deploy this protection method since it will no longer require that every URL be listed for it to be accepted.
  
  
• Improved Statistics Gathering: We corrected a back-end data gathering bug where some of our network appliances were not properly being polled for data.
  
  
• Retiring of Back-end DDoS Mitigation: We retired a feature that allowed some basic configuration for Back-End DDoS Mitigation. This feature was seldom used, especially after the introduction of our very comprehensive Front-End DDoS protection a few years ago.
  
  

Please send us your feedback! As we continue to evolve our solution to be the leading ADC-as-a-Service platform, we want to know what you think. Tell us the good and the bad. Let us know what features you think we should have and which ones are a waste of time, buggy, or don’t make sense. The more feedback you give us, the better our product becomes because we really do listen! Please contact us! We love hearing from our customers.