Aug 20 2021 11:04 AM
I have an Application Gateway with a WAF that is blocking simple passwords that contain a ^
What is the best-practice for allowing special characters in a password field so the WAF does not see this as a potential SQL injection attack?
I am considering a base64 encoding but am looking to verify this is the correct route to take.
Sep 01 2021 12:32 AM - edited Sep 01 2021 12:34 AM
@RexBloom we had same experience and we fixed it.
There are two quick option to fix it:
For us point #1 was the best solution.
Sep 20 2021 11:43 AM