Forum Discussion
ng_export with Per Request Policies
- Jan 30, 2020
You can already do it with normal policies, no reverse engineering needed.
However that ID 755148 refers to API Protection policies. These are the same as PRPs, but they have a different "type" (I'm sure you noticed already).
The other thing is:
The way I do this usually when I'm creating labs or other material is to walk the configuration hirearchy (policy items, agents, policy, profile, customization groups) and then turn it into a pile of TMSH commands, then use the commands to create a policy. It's kind of fragile between versions, but mostly works fine.
Yeah, I was surprised when I installed 15.1 to find the "modern" customization option. I'm glad to see that it's based on Angular as we have a lot of development using that stack. The old style was miserable to customize.
One thing I love about ASM policies is that one can import/export/overwrite at will. This makes promotion VERY easy from NON-PROD to PROD. Granted APM deals with more endpoint data like VPNs. However, when used in an LTM+APM mode for SSO processing the policy is not nearly as complicated.
Thank-you for your help on this.
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