Security Assist - Activate access rules via database

Is there a way to toggle on/off the security access rules via the database. I would like to changes a record in the database that would in turn remove the security assist rules from the header of the page, or add it back in.

There are certain pages I want visible tot he public at times, but want to easily lock them back down without having to go back into the code. Making the change in the CMS (database) would be ideal.

Any ideas how to structure this without jeopardizing security?

Thanks

I dont think i would do this through the database, using the database would require a query on every protected page, that would add a lot of traffic to the database, on a busy site, that could add up.

you could create a file in your site that you attach to all of the pages at line 1 before any of the security assist code to set a session to 1 or 0:

<?php

@session_start();

$_SESSION['makeProtected'] = "1";

?>

then add an if statement around the security assist page access code so it will be bypassed if the makeProtected session is not 1:

<?php if(isset($_SESSION['makeProtected']) && $_SESSION['makeProtected'] == "1") { ?>

<?php

if (!WA_Auth_RulePasses("Logged in to visitors")){

    WA_Auth_RestrictAccess("login.php");

}

?>

<?php } ?>

to unlock the pages, set the makeProtected session to something other than 1.

I tried your session code, but I am prompted a header error:

Warning: Cannot modify header information - headers already sent by (output started at /nfs/c06/h05/mnt/153609/domains/domainname/html/project/index.php:8) in /nfs/c06/h05/mnt/153609/domains/domainname/html/WA_SecurityAssist/Helper_PHP.php on line 67

Did you mean to "attach the file" as a php require? Thats what I did before the security assist code blocks in the header.

Attached is my code.

the headers already sent error happens if there is output to the page between php tags.

in your page, i see spaces before the opening php tags on line 4, 5 and 11

there is also a blank space at the end of line 5. these blank spaces are causing the error.