frontend-fingerprint did not match. Session terminated.

matthi

The same here.

rene.bayer

We commented out the last if statement in /usr/share/kopano-webapp/server/includes/controllers/service.fingerprint.php as a workaround

        // Single sign on will never go through the login page. So we cannot check
        // the fingerprint there!
        //if ( OIDC_ISS === "" && !WebAppAuthentication::isUsingSingleSignOn() && (!isset($_SESSION['frontend-fingerprint']) || $_POST['fingerprint'] !== $_SESSION['frontend-fingerprint']) ){
        //       error_log('frontend-fingerprint did not match. Session terminated. ' . WebAppAuthentication::getUserName());
        //        $phpSession->destroy();
        //        Response::unAuthorized();
        //}

steph32

@rene-losert said in frontend-fingerprint did not match. Session terminated.:

mmented out

It seems to work.
Thank you very very much.

Stephane.

laurensb

Is this the solution? It doesn’t seem right to disable security checks to work around bugs.

It surely must be possible to solve this bug so that it works fine again with Firefox without just discarding security checks, right?

bioProjekt GmbH

Hi,

since Firefox 91.1.0esr the problem doesn’t occur anymore. Can anybody confirm this? Did Firefox changed its bevaviour?

Thanks and greets
Stephan

loloca

@bioprojekt-gmbh
Hi,
our customers and employees also complain about this problem. Unfortunately it cannot be solved yet.
Thanks, Siegfried

Manuel1948

@bioprojekt-gmbh Cant’ confirm, but in normal Firefox version 94.0.2 64bit the problem is still occurring.

Manuel1948

Dear people,

the browser executes a javascript function, which sends a fingerprint (special id) to the server (at logon request) and later at login the server checks if the fingerprint is the same.
In Firefox (my version 94.0.2 64bit) the second fingerprint differs from the first one.

I investigated this issue a little bit further and found out that this fingerprint is based on fonts, which the browser can load from the OS, so basically which fonts from a given array are installed, and which are not.

In this case the “Arial Narrow” font isnt recognized at the earlier check, but then later it is, so that why the fingerprint differs - don’t ask me why?

The workaround/solution is to remove this “Arial Narrow” font from the javascript, so that the fingerprint doesn’t change because of it.

Workaround/Solution
In /usr/share/kopano-webapp/client/fingerprint.js search for Arial Narrow; and remove it from this file (marked green), save it and you should be good to go.

laurensb

@manuel1948 Works for me, many thanks for investigating this and sharing a solution!

bioProjekt GmbH

Hi,

last week we ran into this again. Last time we didn’t need to integrate the workaround Manuel mentioned, today we did. Let’s see if things get better. Is this a known bug?

Greets
Stephan