OAuth.php

After upgrading I have used Security Assist, I'm getting this message on the login page

Warning: require(phpmailer/src/OAuth.php): failed to open stream: No such file or directory in /home/mysite/public_html/webassist/email/WA_Email.php on line 9

Fatal error: require(): Failed opening required 'phpmailer/src/OAuth.php' (include_path='.:/opt/cpanel/ea-php72/root/usr/share/pear') in /home/mysite/public_html/webassist/email/WA_Email.php on line 9

Who creates these files? if web assist does, they aren't being created.

I'm working on that right now... SecurityAssist doesn't create the files. To get them created just apply "send email message" to a dummy page and then you can upload them.

I'm only creating a login and password field, dont need register, email, forgot. Can you just send me one?

It is a folder filled with files. If you just create a blank page and then apply "send email message" you can delete the page after and upload the webassist/email/phpmailer folder.

I'm going to need some help with this. I have a bunch of pages already coded to use

<?php require_once( "../webassist/security_assist/helper_php.php" ); ?>
<?php
if (!WA_Auth_RulePasses("Logged in to HQStaff")){
WA_Auth_RestrictAccess("NoGo.php");
}
?>

I got the file OAuth.php created but all of my pages are failing now. I can now log in but the pages using code to secure them all fail now. I can take off the security and re-work all of those files if a new approach is working.

If you have the new login save the same session variable names as the old one, then the restrict access server behaviors on those pages shouldn't need to be updated at all.

I have 4 different login pages for access to different things. whatever this change was killed all 4 of these logins. I haven't changed any sessionids.

I'm simply controlling access to pages.

What file(s) got changed? Praying I have it still on my laptop at home.

They were all working fine, I created a new one and it kill all my existing ones. They can no longer use the rule that was created.

<?php require_once( "../webassist/security_assist/helper_php.php" ); ?>
<?php
if (!WA_Auth_RulePasses("Logged in to HQStaff")){
WA_Auth_RestrictAccess("NoGo.php");
}
?>

I'd have to see the definition of the rule:
Logged in to HQStaff

to see what session variables it relies on. Then I'd have to look at your new login page to see if it saves those session variables.

I've asked the ISP if a backup was done last night so I can roll back. Would rather go back and loose today than have to work on 30 different files since there is not a fix.

They (all login pages and the secured files) were all working just fine till this afternoon when I decided to use security assist to create a new log in page. Doing that broke all of the existing log in pages any of the pages that were secured previously.

You shouldn't have to update all 30 pages. You would likely just have to make sure the login page saved the same session variables. The other pages would not need to be updated. If I saw the login page and the security rule I could likely tell you what was missing.