I’m not getting it. I worked with Security Providers with DB (Sqlite / MySQL) and that works. But for a small admin Panel I dont want to setup a whole Table/Permission/Query as that temp admin panel is only needed 2-3 weeks.
Now I have a login.php and admindashboard.php and on both I need to place security provider right? And then comes the strange thing: Do I need a security provider with logindata+password for login.php and admindashboard.php ??? Would mean I would have that static logindata completely twice ??
So i would have a security provider with admin logins for each Page?? I thought that would be a file which would be linked. Or do I make a mistake??? So for now if a userlogin changes, I would change that on all security providers, as each uses its own “variant” of userlogins…
You create your security provider than you can apply that security to any page in app connect. Don’t secure login.php or nobody can access it!
Once created you can save the security provider as a linked file
The logic is the same as with database security provider.
It’s just the login type is different (not coming from a DB).
Apply the security as on the rest of your pages.
In server connect panel you define the security settings for the whole site. I.e. define the source for usernames, passwords, permissions.
With the security enforcer you restrict access to the pages using the defined users, passwords.
… ???
