Skip to content

[stable35] fix(jsignpdf): improve the diagnosis of TSA failures - #8279

Merged
vitormattos merged 2 commits into
stable35from
backport/8274/stable35
Sep 6, 2026
Merged

[stable35] fix(jsignpdf): improve the diagnosis of TSA failures#8279
vitormattos merged 2 commits into
stable35from
backport/8274/stable35

Conversation

@backportbot-libresign

Copy link
Copy Markdown

Backport of PR #8274

checkTsaError() and checkHashAlgorithmError() throw before the
logger->error() call in signWrapper(), so the original message from
JSignPdf never reached nextcloud.log. That message is the only place
where the real cause of a signing failure is described: the reporter of
#8145 found it by running JSignPdf by hand.

Log first, then translate the error into the friendly message the user
sees.

Signed-off-by: André Maia <andrefnkmm@gmail.com>
Assisted-by: Claude Code:claude-opus-5
checkTsaError() triggers on TSAClientBouncyCastle, UnknownHostException
and Invalid TSA, and always asked the admin to check DNS, network and
firewall connectivity. When the authority answers with an HTTP status the
server was reached and rejected the request, so that hint points at the
wrong place: Certum replies 400 to a SHA-1 timestamp query, and #8145
reports the connectivity message for it.

Report the status and the endpoint that answered in those cases, and
point at what the authority expects. UnknownHostException and Invalid TSA
keep the current message, where the connectivity hint is correct.

Signed-off-by: André Maia <andrefnkmm@gmail.com>
Assisted-by: Claude Code:claude-opus-5
@github-project-automation github-project-automation Bot moved this to 0. Backlog in Roadmap Sep 6, 2026
@backportbot-libresign backportbot-libresign Bot added this to the Next Major (35) milestone Sep 6, 2026
@vitormattos
vitormattos merged commit b437a01 into stable35 Sep 6, 2026
65 checks passed
@vitormattos
vitormattos deleted the backport/8274/stable35 branch September 6, 2026 14:54
@github-project-automation github-project-automation Bot moved this from 0. Backlog to 4. to release in Roadmap Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 4. to release

Development

Successfully merging this pull request may close these issues.

2 participants