Forum Discussion
Walter_Kacynski
Cirrostratus
Cirrostratusng_export with Per Request Policies
Does anyone know if ng_export cli will work with per request policies (PRP). Access Profile Export utility v14.1 Usage: ng_export [-t|-type access_policy] <name> <filename> [-p|-partition <pa...
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.
Walter_KacynskiCirrostratus
CirrostratusI see, so you would use a lab box exclusively. The only challenge is that there once this config is live on a box, making changes become difficult as one would have to change all virtuals referencing the updated profile(s).
I'm going to 15.1 ASAP, is there something that is notability different for profile duplication?
It would REALLY be awesome if access profiles worked like ASM policies. A single XML file with all the customization groups.
- Lucas_Thompson
Employee
Agreed, yeah it would be nice. APM's schema is pretty complicated compared to ASM. But in the end these are all MCP objects that you can create with TMSH (aside from the files that appear in cache-path of various MCP objects).
15.1 brings a much more effective customization system that has a better separation of code and content, so instead of re-writing existing pages you just use CSS overrides in "user-*" files in customization groups.
15.1's login pages, message boxes, and webtop also uses Angular now instead of the proprietary mechanism used in older versions. So an Angular dev should be able to easily customize.
We're working on a customization example guide and hope to have it published on clouddocs (or here) in the next month or so.