Document Generation – /p/ Path Based Access Restriction
0
Hi all,I'm currently setting up the Document Generation module for our Mendix application. Document generation is working correctly in our Acceptance environment, but in Production we receive the following error when attempting to generate a PDF:"DOCGEN_NAVIGATION_ERROR: Failed to navigate to page due to an invalid response code: 403."After enabling Trace logging for DocumentGeneration, we can see that the request to the Document Generation service is successful and returns a 200 response. The callback to /docgen/generate also appears to be successful. However, immediately before the 403 error, the log shows:Using custom URL prefix 'p/'I noticed a difference in the Path Based Access Restrictions between our environments:Acceptance/p/ → N/A (inherit from top level path /)Production/p/ → Deny all accessThe top-level / path in Production is currently set to Allow all access, and /docgen/ is also set to Allow all access.It therefore looks like the /p/ restriction in Production may be preventing Document Generation from navigating to the page it needs to render.Would it be safe/recommended to change /p/ in Production from Deny all access to N/A (inherit from top level path /) to allow Document Generation to work?I'm particularly interested in understanding whether changing this setting introduces any security implications or exposes functionality that would otherwise be inaccessible.