Admin Passphrase not recognized

Question

Admin Passphrase not recognized

Closed this issue 3 years ago · 7 comments

What I did 📝

I followed the instructions at https://help.passbolt.com/hosting/install/ce/docker.html and I managed to successfully run the service and create the admin user.

I even received an activation e-mail, having configured e-mail delivery using EMAIL_TRANSPORT_DEFAULT_HOST, EMAIL_TRANSPORT_DEFAULT_PORT, EMAIL_DEFAULT_FROM, EMAIL_DEFAULT_FROM_NAME

I used the activation link to setup the admin user and kept in a safe place both the passphrase and the PGP key (recovery kit).

What happened 💥 📋

After successful setup of the admin user I was asked to enter the passpharse to authenticate but the authentication failed without errors and I was just redirected to the same login page.

I deleted the service and the data volumes and repeated the installation process more than once in case I hadn't saved the passphrase correctly but unsuccessfully.

The outcome was the same with both the "root" and "non-root" Docker images

What I expected to happen

I expected successful first login.

Answer 1 · 2022-02-06T17:32:52.000Z

When using the eye icon and viewing the passphrase can you confirm it's as expected ( ie without extra spaces)? Anything unusual about the passphrase? How are you entering it: manually, or pasting?

Answer 2 · 2022-02-06T17:39:12.000Z

I am pasting but I have checked character by character using the eye icon, the passphrase is correct.

Answer 3 · 2022-02-06T17:45:53.000Z

What if you use a different passphrase? (or have you done that already)

Answer 4 · 2022-02-06T17:46:35.000Z

The passphrases I used meet all the requirements, special characters, numbers, letters etc.
but even simple passphrases without special characters didn't work.

Answer 5 · 2022-02-06T18:02:48.000Z

I have just tried with earlier version "3.4.0-ce-non-root" and simple passphrase but same outcome unfortunately.

Answer 6 · 2022-02-06T18:07:54.000Z

I'm thinking it's not a passphrase bug. Possibly something in your setup that is clearing the browser cache between requests, or something like that. Or the web server is unhelpfully caching the csrf token instead of allowing it to refresh.

Answer 7 · 2022-02-06T18:35:20.000Z

Indeed, it was browser related finally, I should have thought about this.
I cleared everything I could including the CSRF token and I managed to login.