Forum Discussion
chaining with other WAF
Hi,
For migration to F5 devices purpose, we will chain F5 with the current WAF. Then remove current one after validating the ASM policies. We'll put the F5 in transparent mode for learning the traffic and build the policies. The flow will go to current WAF and then to endpoint (see pict below).
We will import the SSL certificates/keys of apps from current WAF to F5.
Question: how can we configure the client and server SSL profiles and avoid disturbing the apps during this chaining period? Current WAF should also keep the certificates/keys.
Client SSL profile with imported cert/key ?
Server SSL profile with imported cert/key ? default profile ?
Thanks for your help.
- Leonardo_SouzaCirrocumulus
Interesting drawing. :P
Try this in the future:
You can use the standard setup with clientssl and serverssl, but that means ASM will terminate the SSL connection and start again. However, there are some useful options in the ssl profile. I never remember which one is for what, so here is both:
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com