Project

General

Profile

Actions

Bug #21925

closed

login with felogin does not work in the same browser as the backend

Added by Sonja Schubert almost 15 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
felogin
Target version:
-
Start date:
2010-01-08
Due date:
% Done:

0%

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

Description

When I'm logged in in the backend of 4.3.0 with firefox I cannot login in the frontend with felogin. It displays always the "username or password wrong" error message. When I'm not logged in in the backend the felogin login works also in firefox.

TYPO3 4.3.0
felogin 1.2.0
firefox 3.5.7
RSA support for FE and BE enabled
saltedpassword system extension enabled
(issue imported from #M13175)

Actions #1

Updated by Benni Mack almost 15 years ago

Hey Sonja,

maybe this is related to either RSA support or the saltedpassword sysext. Could you try and reproduce this bug again with not having one of the extensions installed?

Thanks,
Benni.

Actions #2

Updated by Sonja Schubert almost 15 years ago

Hi Benni,

I tested the login again without RSA or saltedpassword support enabled and the login does not work. I cleared the FE and localconf cache, deleted the cookie and reset the password as cleartext of the feuser before testing.

Kind regards,
Sonja

Actions #3

Updated by Guenter Koch almost 15 years ago

Hello,

same problem after updating to Firefox 3.5.7
TYPO3 4.3.0
felogin 1.2.0

guenterk

Actions #4

Updated by Sonja Schubert almost 15 years ago

But I think its not a problem of firefox 3.5.7, I had the problem already on 3.5.x

Actions #5

Updated by David Bruchmann almost 15 years ago

Do you use a firewall or a proxyserver?

Actions #6

Updated by Sonja Schubert almost 15 years ago

Yes we use a firewall to get to the website and no, no proxy.

Actions #7

Updated by David Bruchmann almost 15 years ago

Can you try to reach the page without firewall?

Which kind / product of firewall you're using?

Actions #8

Updated by Sonja Schubert almost 15 years ago

I tried again without firewall by another network and I can't login too. So I think it's not the firewall.

Actions #9

Updated by David Bruchmann almost 15 years ago

What's about the connection (perhaps it's clear when RSA is known) is it http or https or different for FE and BE.
One idea is that perhaps two individual sockets are required for login in BE and FE. In this case perhaps also a default Software-Firewall (Windows?) of the external PC blocks the connection.
Nevertheless this problem shouldn't only concern Firefox and is only an idea.

Actions #10

Updated by Steffen Kamper almost 15 years ago

i will take care of tomorrow and see if i can fix.
As it works as expected on my installations, may be you have an account of one installation where the bug appear?

Actions #11

Updated by Dimitri Koenig almost 15 years ago

any further progress?

Actions #12

Updated by Dimitri Koenig almost 15 years ago

i found the problem: feeditadvanced

it inserts the following tsconfig code:
admPanel.override.preview = 1

i had not enough time to take a deeper look but the problem is somewhere located in:
sysext/cms/tslib/class.tslib_adminpanel.php and class.tslib_fe.php > determineid:
$simUserGroup = $GLOBALS['BE_USER']
>adminPanel->extGetFeAdminValue('preview', 'simulateUserGroup');
it returns the value of admPanel.override.preview.
very strange...

Actions #13

Updated by Dimitri Koenig almost 15 years ago

temporary solution is to add the following tsconfig code to the admin tsconfig:
admPanel.override >

Actions #14

Updated by Dimitri Koenig almost 15 years ago

small update: it should be:
admPanel.override.preview >

but i still try to figure out why it works with some typo3s and with some others it doesn't...

Actions #15

Updated by Xavier Perseguers almost 13 years ago

  • Assignee deleted (Steffen Kamper)
  • Target version deleted (0)
  • TYPO3 Version set to 4.5
Actions #16

Updated by Alexander Opitz over 11 years ago

  • Status changed from Accepted to Needs Feedback

The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #17

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

No feedback for over 90 days.

Actions

Also available in: Atom PDF