Hi @Duffman,
Looking at the warnings and help they seem to be irrelevant to this issue.
Debug was intentionally set to true in hopes that i would be able to get more information to try and solve the issue. Though just for a santity check i set debug to false to see if it would fix the issue it did not.
You mentioned that the passbolt server must be secure and as far as i can tell it is (ssl cert, jwt token, gpg cert and key).
Addititional things i have tried.
- Upgraded 4.1.0 - no improvement
- cleared the database and reinstalled - no improvement
After doing all this i found the mobile faq help page, when running the below script i got “JWT key and pem doesn’t match”, at first ignored it since the healthcheck output “[PASS] A valid JWT key pair was found”. Though as a last ditch effored i generated new jwt key and cert rather than letting the helm scripts do it. The new JWT key worked and i can login using the mobile app!
if openssl rsa -in /etc/passbolt/jwt/jwt.key -outform PEM -pubout 2>/dev/null | diff /etc/passbolt/jwt/jwt.pem - > /dev/null; then echo "OK: JWT key matches with JWT pem"; else echo "NOT OK: JWT key and pem doesn't match"; fi
To Fix
ssh-keygen -t rsa -b 4096 -m PEM -f jwt.key
openssl rsa -in jwt.key -pubout -outform PEM -out jwt.key.pub
cat jwt.key | base64 -w 0
copy the output to jwtServerPrivate in values.yaml
jwtServerPrivate: "string with base64 private key"
cat jwt.key.pub | base64 -w 0
copy the output to jwtServerPublic in values.yaml
jwtServerPublic: "string with base64 public key"