iOS App: "Resouce secret is invalid" with shared folder

Community Feedback
1

Hi,

when I add a new entry to a shared folder, everything works fine. The entry is saved without any issues.
However, if I try to edit this or any other entry in the shared folder, I get an error message when saving: “Resource secret is invalid.”

If I make changes to an entry in my own folder, it works without any problems.
So, the error only occurs with shared folders.

When i use the Firefox Addin, all works fine.

It’s a fresh installation, with only some test users.

My App Log:

Passbolt:
Device: iPhone
OS: 18.1.1
App: 1.21.0
----------
[2025-01-13 08:36:22] ⚠️ InvalidResourceSecret
DiagnosticsContext:
•Failed to encrypt secret for all required users! PassboltResources/ResourceEditForm+Passbolt.swift:118
⮑ "path": 118
⮑ "file": PassboltResources/ResourceEditForm+Passbolt.swift
[2025-01-13 08:36:25] ⚠️ InvalidResourceSecret
DiagnosticsContext:
•Failed to encrypt secret for all required users! PassboltResources/ResourceEditForm+Passbolt.swift:118
⮑ "path": 118
⮑ "file": PassboltResources/ResourceEditForm+Passbolt.swift
[2025-01-13 08:36:29] ⚠️ InvalidResourceSecret
DiagnosticsContext:
•Failed to encrypt secret for all required users! PassboltResources/ResourceEditForm+Passbolt.swift:118
⮑ "path": 118
⮑ "file": PassboltResources/ResourceEditForm+Passbolt.swift
[2025-01-13 08:36:42] ⚠️ InvalidResourceSecret
DiagnosticsContext:
•Failed to encrypt secret for all required users! PassboltResources/ResourceEditForm+Passbolt.swift:118
⮑ "path": 118
⮑ "file": PassboltResources/ResourceEditForm+Passbolt.swift
[2025-01-13 08:42:22] Wiping passphrase cache...
[2025-01-13 08:51:38] Requesting authorization...
[2025-01-13 08:51:38] [597BA1B9-507E-473F-968C-F12FDDD55C65] HTTP GET /img/avatar/user_medium.png
[2025-01-13 08:51:39] Beginning authorization...
[2025-01-13 08:51:39] [597BA1B9-507E-473F-968C-F12FDDD55C65] HTTP 200 /img/avatar/user_medium.png
[2025-01-13 08:51:40] Access token expired...
[2025-01-13 08:51:40] ...refreshing access token...
[2025-01-13 08:51:40] [50508C2B-AC53-4FB3-B91E-13E558F272A1] HTTP POST /auth/jwt/refresh.json
[2025-01-13 08:51:40] [50508C2B-AC53-4FB3-B91E-13E558F272A1] HTTP 200 /auth/jwt/refresh.json
[2025-01-13 08:51:40] Session refreshed...
[2025-01-13 08:51:40] ...authorization succeeded!
[2025-01-13 08:51:40] Updating account profile data...
[2025-01-13 08:51:40] [722D9E5B-C937-4BC8-BBBF-14A976BB64F9] HTTP GET /users/6a4a7f92-31de-4773-9c4e-c57026f6647f.json
[2025-01-13 08:51:40] [722D9E5B-C937-4BC8-BBBF-14A976BB64F9] HTTP 200 /users/6a4a7f92-31de-4773-9c4e-c57026f6647f.json
[2025-01-13 08:51:40] ...account profile data updated!
[2025-01-13 08:51:42] Wiping passphrase cache...
[2025-01-13 08:51:44] Requesting authorization...
[2025-01-13 08:51:44] [27DCD4EE-239C-4DF6-ACC5-141E556E33E6] HTTP GET /img/avatar/user_medium.png
[2025-01-13 08:51:44] [27DCD4EE-239C-4DF6-ACC5-141E556E33E6] HTTP 200 /img/avatar/user_medium.png
[2025-01-13 08:51:45] Beginning authorization...
[2025-01-13 08:51:45] ...reusing access token...
[2025-01-13 08:51:45] Passphrase provided...
[2025-01-13 08:51:45] ...authorization succeeded!
[2025-01-13 08:51:46] Updating account profile data...
[2025-01-13 08:51:46] [1ECB49EC-6ACD-4C0A-8274-7B8E8F32BF7B] HTTP GET /users/6a4a7f92-31de-4773-9c4e-c57026f6647f.json
[2025-01-13 08:51:46] [1ECB49EC-6ACD-4C0A-8274-7B8E8F32BF7B] HTTP 200 /users/6a4a7f92-31de-4773-9c4e-c57026f6647f.json
[2025-01-13 08:51:46] ...account profile data updated!
1 Like
2

Hello @ASTB ,
Welcome to the forum :slight_smile:

I would like to know if you could run:

  • sudo su -s /bin/bash -c “/usr/share/php/passbolt/bin/cake passbolt cleanup” www-data
    • If you are on a RPM distro, please replace www-data with nginx

Let me know if that helps.

3

Hi
i can run it.

No issue found, data looks squeaky clean!

4

Hi @ASTB,
Do you mean that the issue has been fixed?

5

@grzegorz

This is the program’s response.

The problem is still there

6

Hi @ASTB,

Sorry for the delayed response. You are right! We have added this issue to our backlog, so you can expect it to be fixed soon. I will push for it to be included in the next app release, but I can’t guarantee it.

Thank you for your report!

2 Likes