Project

General

Profile

Actions

Bug #61287

closed

Immediately logged out from FE after felogin

Added by Claudio Strizzolo over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-09-01
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I am upgrading a working site from Typo3 4.5 to 6.2.4. Almost everything seems to work fine except for some pages that should be accessible only by FE users through a felogin form, which worked correctly with 4.5.

The felogin form itself seems to work correctly: if the user supplies the right password, he logs in and can see the protected contents on that page. But if he changes to a different page he loses his "logged-in" status. So if he tries to view another page reserved to FE users he cannot do it, as if he never logged in. Even if he tries to load again the first page (that one that was shown after the initial login), he is not able to do it: the user is reported as if I never logged in and the login form is shown again.

It looks like the user gets logged out immediately.

I tried by playing with the permalogin switch without success.

I am using the ig_ldap_sso_auth extension to authenticate users against a LDAP database. On Typo3 4.5 I used the extension eu_ldap. However, I do not think that the autentication step is reponsible because the user can actually log in through the FE form (BTW, BE users can log in too using the same LDAP database).
No problems at all with the BE, instead.

I looked at the cookies at different steps:

Before login: no cookies

After login and viewing the first protected page, which is the same page as the login page, no redirect to a different page:
cookie: fe_typo_user
value: e52b5...

Jump to another page (not protected):
same cookie

Jump back to the first protected page:
same cookie

Although the cookie is still set, the login form is displayed again. The login form should be displayed only for not logged FE users, instead, so it looks like I am not logged on any more.

Some settings that might be involved follow:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['cookieDomain']

I tried with either an empty string and the address of my site. In both cases I can login to the BE but in the FE I get the wrong behaviour I described.

$GLOBALS['TYPO3_CONF_VARS']['SYS']['cookieSecure']

0

$GLOBALS['TYPO3_CONF_VARS']['FE']['cookieDomain']

Empty string, then the value of $GLOBALS['TYPO3_CONF_VARS']['SYS']['cookieDomain'] should be used.

$GLOBALS['TYPO3_CONF_VARS']['FE']['lifetime']

3600


Files

snap1.png (51.6 KB) snap1.png Claudio Strizzolo, 2014-09-01 15:32
snap2.png (30.2 KB) snap2.png Claudio Strizzolo, 2014-09-01 15:32
snap3.png (62.5 KB) snap3.png Claudio Strizzolo, 2014-09-02 08:27
snap4.png (15.4 KB) snap4.png Claudio Strizzolo, 2014-09-02 08:50

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #60264: felogin permalogin not working with typo3 6.2.x -> cookie expires with sessionClosed2014-07-11

Actions
Actions

Also available in: Atom PDF