Forum Discussion
F5 AWAF/ASM support for wildcard url and parameter names with a swagger/openapi file
Can you please refer
https://f5-agility-labs-waf.readthedocs.io/en/latest/class7/module2/lab4/lab4.html
https://f5-agility-labs-waf.readthedocs.io/en/latest/class7/class7.html
https://docs.cloud.f5.com/docs/how-to/advanced-security/import-swagger-control-api-access
HTH
š
ā
Thanks for the links but they seem not the thing I need at the moment.
I want to create wildcard parameter with importing a swagger/openapi file that will create the wildcard parameter not just creating it from the GUI/CLI or the F5 BIG-IP API as I am aware how to do this as I have many years for experience with AWAF/ASM and as of now I played a lot with Swagger/OpenAPI file imports in ASM/AWAF/XC š .
Also the last link that you provided is for XC Distributed Cloud for the WAAP API protection cloud service not F5 BIG-IP AWAF/ASM as the two products have swagger/openapi import that works in completely different ways.
The correct link is:
https://my.f5.com/manage/s/article/K07241201
If you decide, you can review the two features at the links below as they show feature on AWAF and XC:
https://www.youtube.com/watch?v=F-OwVLsCw-M
https://www.youtube.com/watch?v=fT6i_HDRt9Q
Outside of that I managed to create a parameter with location any from a swagger file , so only the wildcard parameter (except the possible complex workaround of using JSON profile for a parameter match that I mentioned that is a parameter type object in the Swagger file) or using request method "any" or no request method at all (In the F5 GUI you do not need to specify one) seems an issue at the moment.
"parameters": [
{
"name": "test",
"in": "any",
"description": "wildcard path",
"required": true,
"type": "string"
}
],
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