starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #2164] [Bug] 2FA not working when using Envelopes (self-hosted) #628

New issue

Closed

opened 2026-02-26 18:47:50 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 18:47:50 +03:00

Owner

Originally created by @Dailson-Allves on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2164

Originally assigned to: @dguyen on GitHub.

Issue Description

Hi,

After updating and starting to use the new Envelope feature, I noticed that the 2FA by email flow stops working properly.

When using the traditional signing flow (single document + 2FA), everything works as expected.
When using Envelope + 2FA, after entering the email code, the document is not sealed or finalized, and backend errors appear.

Steps to Reproduce

Create an Envelope with one or more documents.
Add recipient(s) and enable 2FA by email.
Send the Envelope.
As the recipient, open the link, enter the code received by email, and sign all required fields.
Try to complete the Envelope.

Expected Behavior

After entering the valid 2FA code and signing:

The Envelope should be completed successfully.
The documents should be sealed.
The certificate and audit log should be generated.
Confirmation emails should be sent normally.

Current Behavior

The Envelope signing flow does not complete.
API returns "UNAUTHORIZED – Access authentication required" errors.
The same configuration works fine using the traditional document flow.

Screenshots (optional)

recipient.completeDocumentWithToken
appError: { "code": "UNAUTHORIZED", "message": "Access authentication required" }
auth: null

[JOBS]: Job internal.seal-document failed
Failed to get certificate PDF
browserType.launch: Executable doesn't exist at /home/nodejs/.cache/ms-playwright/...

code: 'EMESSAGE',
response: '552 4.3.1 Message size exceeds fixed maximum message size'
command: 'DATA'

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

Chrome, Edge, Firefox

Version [e.g., 2.0.1]

2.0.6

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @Dailson-Allves on GitHub (Nov 10, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2164 Originally assigned to: @dguyen on GitHub. ### Issue Description Hi, After updating and starting to use the new **Envelope** feature, I noticed that the **2FA by email** flow stops working properly. - When using the traditional signing flow (single document + 2FA), everything works as expected. - When using **Envelope + 2FA**, after entering the email code, the document is not sealed or finalized, and backend errors appear. <img width="504" height="165" alt="Image" src="https://github.com/user-attachments/assets/1a92f16f-6e0a-4d80-9610-1870b3daa108" /> ### Steps to Reproduce 1. Create an Envelope with one or more documents. 2. Add recipient(s) and enable **2FA by email**. 3. Send the Envelope. 4. As the recipient, open the link, enter the code received by email, and sign all required fields. 5. Try to complete the Envelope. ### Expected Behavior After entering the valid 2FA code and signing: - The Envelope should be completed successfully. - The documents should be sealed. - The certificate and audit log should be generated. - Confirmation emails should be sent normally. ### Current Behavior - The Envelope signing flow does not complete. - API returns "UNAUTHORIZED – Access authentication required" errors. - The same configuration works fine using the traditional document flow. ### Screenshots (optional) recipient.completeDocumentWithToken appError: { "code": "UNAUTHORIZED", "message": "Access authentication required" } auth: null [JOBS]: Job internal.seal-document failed Failed to get certificate PDF browserType.launch: Executable doesn't exist at /home/nodejs/.cache/ms-playwright/... code: 'EMESSAGE', response: '552 4.3.1 Message size exceeds fixed maximum message size' command: 'DATA' ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] Chrome, Edge, Firefox ### Version [e.g., 2.0.1] 2.0.6 ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [x] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:50 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:51 +03:00

Author

Owner

@dguyen commented on GitHub (Nov 11, 2025):

Thanks, we'll get a fix in for that soon

@dguyen commented on GitHub (Nov 11, 2025): Thanks, we'll get a fix in for that soon

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#628

No description provided.

Rows
Columns