Mobile App - "invalid password"

Installation Issues
1

Is there a problem with Mobile App. I have added the two env variables to my docker container. I can setup the phone key until i get to enter the password. All I get is an invalid password. I have verified that the password is right, and timing is correct (GPG Key timing). but I can not finish the mobile setup. Below is docker container.

version: ‘3.9’
services:
db:
image: mariadb:10.3
restart: unless-stopped
environment:
MYSQL_RANDOM_ROOT_PASSWORD: “true”
MYSQL_DATABASE: “passbolt”
MYSQL_USER: “passbolt”
MYSQL_PASSWORD: “password”
volumes:
- database_volume:/var/lib/mysql

passbolt:
image: passbolt/passbolt:latest-ce
#Alternatively you can use rootless:
#image: passbolt/passbolt:latest-ce-non-root
restart: unless-stopped
depends_on:
- db
environment:
APP_FULL_BASE_URL: ##VALID URL HERE###
DATASOURCES_DEFAULT_HOST: “db”
DATASOURCES_DEFAULT_USERNAME: “username”
DATASOURCES_DEFAULT_PASSWORD: “password”
DATASOURCES_DEFAULT_DATABASE: “passbolt”
PASSBOLT_PLUGINS_JWT_AUTHENTICATION_ENABLED: TRUE
PASSBOLT_PLUGINS_MOBILE_ENABLED: TRUE
EMAIL_DEFAULT_FROM_NAME: “Support”
EMAIL_DEFAULT_FROM: “WORKS”
EMAIL_TRANSPORT_DEFAULT_HOST: “smtp.sendgrid.net”
EMAIL_TRANSPORT_DEFAULT_PORT: “587”
EMAIL_TRANSPORT_DEFAULT_TLS:
EMAIL_TRANSPORT_DEFAULT_USERNAME: “apikey”
EMAIL_TRANSPORT_DEFAULT_PASSWORD: “KEYHERE”
PASSBOLT_PLUGINS_JWT_AUTHENTICATION_ENABLED: TRUE
PASSBOLT_PLUGINS_MOBILE_ENABLED: TRUE

volumes:
  - gpg_volume:/etc/passbolt/gpg
  - jwt_volume:/etc/passbolt/jwt
command: ["/usr/bin/wait-for.sh", "-t", "0", "db:3306", "--", "/docker-entrypoint.sh"]
ports:
  - 90:80
  - 1243:443
#Alternatively for non-root images:   
# - 8080:80
# - 4443:433

volumes:
database_volume:
gpg_volume:
jwt_volume:

2

Hi @distrust Welcome to the forum!

No one else has said anything yet. I had this problem awhile back because I was unknowingly pasting a space. Are there any errors in /var/log/passbolt?

Also here is the main reference for mobile troubleshooting, like debug logs. If you can produce a log and list that would be helpful. Passbolt Help | iOS / Android Mobile FAQ

3

error.log file is empty

image
image1221×271 15.9 KB

4

docker logs shows this when trying to connect (unhelpful)
72.19.0.1 - - [15/Dec/2022:00:42:46 +0000] “POST /auth/jwt/login.json HTTP/1.1” 400 250 “-” “okhttp/4.9.3”
2022-12-15 00:42:46,905 INFO reaped unknown pid 3026 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3028 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3031 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3033 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3036 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3038 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3040 (exit status 0)
2022-12-15 00:42:46,905 INFO reaped unknown pid 3042 (exit status 0)
2022/12/15 00:42:46 [info] 158#158: *275 client 172.19.0.1 closed keepalive connection

5

But this is helpful to see and confirms what you are saying. How about debug logs in mobile app?

6

here are the debugs, after a ‘Successful’ login

Device: samsung SM-S908U1
Android 13 (33)
Passbolt 1.10.0-13


10:45:14 PM --> PUT https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json h2 (41-byte body)
10:45:14 PM <-- 200 https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json (71ms, unknown-length body)
10:45:14 PM --> PUT https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json h2 (41-byte body)
10:45:14 PM <-- 200 https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json (66ms, unknown-length body)
10:45:15 PM --> PUT https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json h2 (41-byte body)
10:45:15 PM <-- 200 https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json (67ms, unknown-length body)
10:45:16 PM --> PUT https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json h2 (41-byte body)
10:45:16 PM <-- 200 https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json (76ms, unknown-length body)
10:45:16 PM Saving private key.
10:45:16 PM --> PUT https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json?contain%5Buser.profile%5D=1 h2 (38-byte body)
10:45:16 PM <-- 200 https://pass.secone.llc/mobile/transfers/3df10faa-2be2-4785-9cab-44b593cf0c56/d27c1ff0-88a2-46fc-ba44-fce9347be747.json?contain%5Buser.profile%5D=1 (161ms, unknown-length body)
10:45:18 PM Checking biometry state
10:45:41 PM Passphrase cache cleared
10:45:41 PM Passphrase cached
10:45:41 PM Getting server pgp and rsa keys
10:45:41 PM --> GET https://pass.secone.llc/auth/verify.json h2
10:45:41 PM <-- 200 https://pass.secone.llc/auth/verify.json (117ms, unknown-length body)
10:45:41 PM --> GET https://pass.secone.llc/auth/jwt/rsa.json h2
10:45:42 PM <-- 200 https://pass.secone.llc/auth/jwt/rsa.json (118ms, unknown-length body)
10:45:42 PM Getting server pgp and rsa keys succeeded
10:45:42 PM Verifying server fingerprint
10:45:42 PM Server key fingerprint is valid
10:45:42 PM Preparing sign in challenge
10:45:42 PM Prepared sign in challenge
10:45:42 PM Signing in
10:45:42 PM --> POST https://pass.secone.llc/auth/jwt/login.json h2 (1639-byte body)
10:45:42 PM <-- 400 https://pass.secone.llc/auth/jwt/login.json (215ms, unknown-length body)
10:45:42 PM Failure during sign in: The credentials are invalid.
7

Thank you this is very helpful for the team as they review your posts.