Thread

Hello,

I’m working on a new EE site. To avoid that other people can access the site/template while I am working on it, I made sure some templates are only accessible by members of a certain member group.

However, when I try to access such a restricted template, EE doesn’t accept my username and password. Eventhough username and password are correct.

Does anyone have an idea what the problem is?

Thanks a lot!

Hi drawingcloudsintheair,

When you access this page it sounds like you’ve set up a redirect so that you can login and then view the page. Is this correct? If so then login is not working on the front end of the site, are you able to login to the CP of the site using the same login credentials? i.e by going to http://domain.com/admin.php?

Is this user the super admin user? If not, does their member group have access to this particular template?

Sean

Hi Sean,

Thanks for your reply.

When you access this page it sounds like you’ve set up a redirect so that you can login and then view the page. Is this correct?

There’s no redirect, I think. But yes, when I access the page, the browser asks for usersname and password and I should be able to see the page/template.

Yes, I can login to the control panel with the same login credentials.
This user is not a super admin user. I created this user only for the purpose of accessing these restricted templates and is part of the member group which has access to these templates. In the past, this setup worked just fine. Now I can’t figure out why it’s not working anymore.

I’m not sure if this helps anything, but here is the screenshot of my settings. «Front End Dev Group» is the member group which has access to the restricted template.

Edit: I created this setup according to this article

Maurus

Hey Maurus,

Can you let me know what version of ExpressionEngine you are running for this site?

I recall a bug in prior versions dealing with HTTP Authentication.

So, letting me know the version will help.

Thanks!

Hi Kyle

The site is running ExpressionEngine v2.4.0 - Build: date 20120123

Maurus

Hey Maurus,

Thanks for that info.

Can you do me a favor and create another dummy member and assign it to the member group in question and attempt to access the page using this new member’s credentials?

Let me know if this member can successfully get through.

If that doesn’t work, can you try turning off HTTP Authentication, and seeing if just logging in via a regular login form gives you access to the page, as opposed to an HTTP login?

Let me know what happens.

Thanks.

Hi Kyle

Can you do me a favor and create another dummy member and assign it to the member group in question and attempt to access the page using this new member’s credentials?

I created a new user. Same behavior. I can login to the CP but not access the restricted template.

When I disable HTTP Authentication (and log out as super admin) and access that template, I get a blank page.

Maurus

Hi Maurus,

I set up a scenario to mimic your situation. I was unable to replicate your problems. I used the same process as outlined in the Devot:ee article.

A couple of things to check:
1) Are you using .htaccess at all? If so, can you post the contents here?
2) Have you verified with the site’s host that they support HTTP Authentication?

I look forward to your reply!

Cheers,

Hi Dan

1) Are you using .htaccess at all? If so, can you post the contents here?

Yes, here is it’s content:

RewriteEngine On 
RewriteCond %{REQUEST_FILENAME} !-f 
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ /index.php/$1 [L]

AddHandler php5-fastcgi .php .php5

2) Have you verified with the site’s host that they support HTTP Authentication?

Maurus

Nope, but I have used this setup before (on the same host) and it worked just fine.

Hi Maurus,

I did a quick search on Google regarding HTTP Auth with php as fast CGI.

On the other instances where this worked, was PHP running as Fast CGI as well? From the search, it looks like that could be the root of the issue here.

Cheers,

Thanks for your post, Dan.
Am I correct that there’s no solution to this problem?

When I remove the fast-cgi line from the .htaccess file, ExpressionEngine doesn’t seem to work anymore.

I never used this method anywhere else than on the setup I’m using it now.

Hey drawingcloudsintheair,

It sounds like this will not work.

Are there other options you can switch to?

If we can do anything else to help, please let us know.

Cheers,

Hi Shane

It looks like it has something to do with the fact that I placed my EE system folder above webroot?
I get the following error message: http://designbymaurus.com/screenshot.png

Do you think the following feautre would work again if I move the system folder back to the public_html directory?

Maurus

Hey Maurus,

What hosting provider do you use?

I am curious about this because I know some hosts have restrictions on these kinds of things.

Cheers,

What hosting provider do you use?

I am curious about this because I know some hosts have restrictions on these kinds of things.

This one: http://www.metanet.ch/