This topic contains 3 replies, has 2 voices. Last updated by Bruce 3 years, 11 months ago.
Topic Author | Topic |
---|---|
Posted: Wednesday Jan 30th, 2013 at 11:34 am #40004 | |
Looking for some advice about the best way to exclude a specific URL from S2 protection. Here is the scenario: We’ve installed a chat program which interfaces with WP but is installed outside of the WP installs on the server. This works perfectly. People who visit our site, who are not logged in, cannot access the chat program. S2 is functioning perfectly. However, it is locking out admins from the admin log in. The URL which is set up to administrate the new chat software is: http://domain/chatprogram/admin/ When a logged in Admin to our membership site manually puts the correct URL into the browser, S2 immediately redirects to the membership website login page. I was thinking the best way to solve this problem would be to add the URI /admin/ to our highest membership level so only the top membership level wouldn’t be redirected away from an admin URL outside of the WP install but then I wasn’t sure if this was the best way given that admin URLS present security risks. Is there any other way to protect a specific URL? I’d appreciate some input.
|