Skip to content

Conversation

@vitormattos
Copy link
Member

No description provided.

When background jobs execute signing operations for unauthenticated signers
(e.g., via WhatsApp), they run in a different session context than when the
visual elements were uploaded. This caused the system to fail finding the
signature files, resulting in the error 'You need to define a visible
signature or initials to sign this document.'

The fix makes getNode() always attempt to retrieve files by nodeId using
folderService->getFileByNodeId(), which searches across the entire signature
folder tree regardless of session. Only if that fails does it fall back to
session-based lookup for backward compatibility.

This resolves signing failures for external signers who properly defined
their visual signature elements.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Add test coverage for the scenario where an unauthenticated signer (e.g., via
WhatsApp) has uploaded signature elements that are stored in the folder
service but accessed from a different session context during background job
execution.

This test verifies that the system can successfully locate and use signature
files by their nodeId even when the session context differs from the upload
context.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
@vitormattos vitormattos added this to the Next Major (34) milestone Jan 23, 2026
@vitormattos vitormattos self-assigned this Jan 23, 2026
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Jan 23, 2026
@vitormattos
Copy link
Member Author

/backport to stable33

@vitormattos
Copy link
Member Author

/backport to stable32

@vitormattos
Copy link
Member Author

/backport to stable32

@vitormattos vitormattos merged commit ca5877a into main Jan 23, 2026
56 checks passed
@vitormattos vitormattos deleted the fix/signature-elements-without-session branch January 23, 2026 19:38
@github-project-automation github-project-automation bot moved this from 0. Needs triage to 4. to release in Roadmap Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 4. to release

Development

Successfully merging this pull request may close these issues.

2 participants