Forum Discussion

Check1t_282465's avatar
Check1t_282465
Icon for Nimbostratus rankNimbostratus
Jul 13, 2017

Unable to edit ASM Policy while Auto Detecting Application Language

I created an ASM Policy and opted to Auto Detect Application Language. After saving, I notice that I am unable to edit (ex: switch policy to Transparent mode). ASM returned message that

 

The Security Policy cannot be modified while Policy Builder is detecting a language. You should either: 1) Wait for Policy Builder to finalize the language detection. 2) Set the language manually.

 

I recall seeing this previously when attempted to change Application Language but not other policy options. Is this 'correct' behavior? Version is BIG-IP 12.1.2 Build 0.0.249 Final.

 

ASM Advanced WAF
security

4 Replies

Sort By
  • Ashwin_Venkat's avatar
    Ashwin_Venkat
    Icon for Employee rankEmployee
    Jul 14, 2017

    Yes, this is expected behavior that you are observing. Anything you configure within the policy is dictated by the application encoding language being used and it is how ASM parses through the request as well. With automatic learning enabled, you are leaving it to the policy builder to learn the language used by the application and make the decision. Alternatively, you can set the application encoding language manually. Once the language is selected, you cannot modify it again within this policy. You will have to re-deploy the policy, in that scenario.

     

  • Ashwin_Venkat_1's avatar
    Ashwin_Venkat_1
    Historic F5 Account
    Jul 14, 2017

    Yes, this is expected behavior that you are observing. Anything you configure within the policy is dictated by the application encoding language being used and it is how ASM parses through the request as well. With automatic learning enabled, you are leaving it to the policy builder to learn the language used by the application and make the decision. Alternatively, you can set the application encoding language manually. Once the language is selected, you cannot modify it again within this policy. You will have to re-deploy the policy, in that scenario.