Update NAP Doc - Configure App Protect WAF - Custom Policies

[kafeelhasan]

Proposed changes

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[kafeelhasan]

I have hereby read the F5 CLA and agree to its terms

[kafeelhasan]

[mjang]

Hi @kafeelhasan , question:

First, context. We're helping users manage custom policies in a UI.

If I understand correctly, the default file path is /etc/app_protect/conf. If the default file path is OK for the user, why does the user have to enter anything?

Based on my reading of https://docs.nginx.com/nginx-app-protect-waf/v5/configuration-guide/configuration/#file-reference, it looks like the user can create their own file path. So if they want something other than /etc/app_protect/conf, then I think they have to enter that path in the File path text box.

[mjang]

We have two approvals. Will merge once tests pass.

[russokj]

So user must now specify literally the '.json' for the extension to the filename. Why don't we call the filed 'File name' instead of 'Name'? Can I assume we check if the extension is missing (or some other value), and fail fast?
For the file path, are we saying they should not specify '/etc/app_protect/conf/' (i.e., enter only a relative path)? I'm not sure what the 'as the default policies folder' is implying. This seems to imply we can change the default. I believe all custom policies MUST be somewhere under this folder.

[kafeelhasan]

Hi @russokj based on this discussion - https://github.com/nginxinc/nalb-shared/issues/1695
There is .json extension validation added to the file path, so if user doesn't give .json to the file path, it will ask to give that and save button will be disabled.
In the UI, it is mentioned as name, hence the same in the documentation.
Users need to set a complete file path either with default '/etc/app_protect/conf' or their own. - @happyhd can add more on this point.

[happyhd]

Oops, I was wrong, the filePath must be started with '/etc/app_protect/conf', so no custom file path setting is allowed. How about:

• Enter the Name, File path, your policy content, and then select Save. The File path must be set with "/etc/app_protect/conf/" plus a file name with ".json" extension.

[russokj]

I don't believe they can set any filepath other than /etc/app_protect/conf/..., right? @happyhd