Security Enforcer option missing on SPA Content Pages

Is there a way to add security enforcer to php page which is a route page in a Wappler SPA project?

This is for a php project.

Hi @George,

The main page in an SPA allows me to set the Security Provider Enforcer as per this picture:
image

The sub pages in the SPA, however, cannot:
image

Why is that?

Opening pages in a browser without a proper identity (even if the server actions protect the data) exposes unnecessary aspects of the application that could be exploited by a hacker.

Can the functionality of the Security Provider Enforcer be added to the subpages?

Many thanks,

Alex

Yes will add it to the content pages as well

this is really appreciated! Any idea of when this will be available?

Also and out of curiosity – and please forgive my ignorance on application security matters:

I was wondering if there is there any risk of someone “manually” invoking code in the dmx* folders, and getting access to something that they should not.

I don’t mean what is under dmxConnect/api because those are our server action APIs and we’re protecting them, but what about everything else?

Many thanks in advance,

Alex

Hi George,

I’m very interested in this one for all the reasons you can imagine.
Do you have any indication of the time for when this will be made available?

Many thanks in advance,

Alex

This was implemented in Wappler 3.9.2

This topic was automatically closed after 29 hours. New replies are no longer allowed.