Password Protecting Admin scp directory

nwhit

We just upgraded to 1.8.1 from 1.7 something. We always had the admin directory (scp) password protected, but now anyone accessing the front end is asked for a user name and password. If the cancel, it proceeds forward to the page, but every page change asks for user/pwrd. Did something change in the new version so that we can no longer password protect the admin directory?I'm guessing that this would also preclude renaming the scp directory as well since it appears to be requiring to go there even for the front end pages?

ntozier

Q: Did something change in the new version so that we can no longer password protect the admin directory?A: No. How a directory is password protected has nothing to do with osTicket.Q: I'm guessing that this would also preclude renaming the scp directory as

well since it appears to be requiring to go there even for the front

end pages?A: No. There is nothing on the client side that requires the admin side (/scp).

nwhit

Not sure what is happening, but when I delete the htaccess file from the scp directory, no access issues on the front end. But when I use cPanel to password protect the directory and it creates the new htaccess file, anyone going to the public pages gets the challenge form. They can cancel it twice (without filling anything in) and it does go to the page okay, but not sure why it is doing this.Here is the htaccess file. Nothing unusual in there, but it seems to get to the main client pages, it must be calling something from the scp directory. When I remove it, works. When I add it, doesn't work.AuthType BasicAuthName "Reserved Area"AuthUserFile "/home/xxxxxxxx/.htpasswds/public_html/service3/scp/passwd"require valid-user

nwhit

Not sure what was happening. I also deleted the authorized users, then did a new htaccess plus added all the users back. Then it worked. Not sure what was happening, but seems to have cleared up. Thanks.

ntozier

Are you self hosting... or is your site hosted with someone else? If your hosted with someone else I recommend that you contact support for your web host.If you are self hosting, then I would presume that there is a problem with your Apache configuration.