Skip to content

[18.0][FIX] vault: inbox share form token handling and optional file - #987

Open
jans23 wants to merge 1 commit into
OCA:18.0from
Nitrokey:18.0-fix-vault-invalid-token
Open

[18.0][FIX] vault: inbox share form token handling and optional file#987
jans23 wants to merge 1 commit into
OCA:18.0from
Nitrokey:18.0-fix-vault-invalid-token

Conversation

@jans23

@jans23 jans23 commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

The frontend inbox share form showed 'Invalid token' for valid links and wrongly required a file even when a name and secret were provided.

@jans23 jans23 changed the title [FIX] vault: inbox share form token handling and optional file [18.0][FIX] vault: inbox share form token handling and optional file Aug 24, 2026
The frontend inbox share form showed 'Invalid token' for valid links
and wrongly required a file even when a name and secret were provided.

- Resolve the recipient public key for any valid token instead of only
  when the inbox still has accesses left, so a valid link no longer
  reports 'Invalid token'. Distinguish an unknown token from a
  recipient without a key pair with clearer messages.
- Drop the hardcoded 'required' on the file input so name + secret are
  sufficient; the file remains optional (the JS still toggles the
  requirements and the server/model already accept secret or file).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants