Hi, I have an instance with passbolt in version 2.13.5 and we need to update to the latest stable version 3.5.0. The application runs on a Centos7 and Apache web server instead of nginx.
What considerations should I take into account when upgrading? I have doubts about whether the installation was done by script or the installation package.
With package installation on 3.5.0, JWT keys are automatically created for mobile app. With the from-sources installation, you will have to create them, following this documentation: Passbolt Help | How to generate JWT key pair manually
With apache, there is also a known issue with mobile app. Authorization header are ignored if not base64 encoded and you will have to add this rule:
RewriteEngine on
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
Hi, @_jc
I have migrated to version 3.5.0 and it works correctly through the web browser, however when trying to configure it in the mobile application, it generates the following error when scanning the QR code:
failed to update user profile: Authentication is required to continue
I have executed the Passbolt Healthcheck on the passbolt server and it only gives me the following warnings and errors in the SSL section, could it have anything to do with this problem?
[FAIL] SSL peer certificate does not validate
[FAIL] Hostname does not match when validating certificates.
[WARN] Using a self-signed certificate
[HELP] Check Passbolt Help | Troubleshoot SSL
[HELP] cURL Error (60) Peer’s Certificate issuer is not recognized.
It seems your passbolt domain does not match the domain set in your SSL certificate and it can be the problem. This point of the mobile FAQ explain how to check if certificate matches your passbolt domain name.