starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-24 21:36:01 +03:00

[GH-ISSUE #2119] Not referenced on eIDAS trusted lists #611

New issue

Open

opened 2026-02-26 18:47:46 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @tainmar on GitHub (Oct 29, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2119

Feature Description

One of your legacy competitor (which we are using) is telling us that you are not on this list and therefore not compliant with eIDAS : https://eidas.ec.europa.eu/efda/trust-services/browse/eidas/tls

Is it real ?

Use Case

No response

Proposed Solution

No response

Alternatives (optional)

No response

Additional Context

No response

Please check the boxes that apply to this feature request.

I have searched the existing feature requests to make sure this is not a duplicate.
I have provided a detailed description of the requested feature.
I have explained the use case or scenario for this feature.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.
I want to work on creating a PR for this issue if approved

Originally created by @tainmar on GitHub (Oct 29, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2119 ### Feature Description One of your legacy competitor (which we are using) is telling us that you are not on this list and therefore not compliant with eIDAS : https://eidas.ec.europa.eu/efda/trust-services/browse/eidas/tls Is it real ? ### Use Case _No response_ ### Proposed Solution _No response_ ### Alternatives (optional) _No response_ ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [ ] I have searched the existing feature requests to make sure this is not a duplicate. - [ ] I have provided a detailed description of the requested feature. - [ ] I have explained the use case or scenario for this feature. - [ ] I have included any relevant technical details or design suggestions. - [ ] I understand that this is a suggestion and that there is no guarantee of implementation. - [ ] I want to work on creating a PR for this issue if approved

kerem added the

Stale

status: triage

labels

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

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Oct 29, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Oct 29, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

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

Author

Owner

@ElTimuro commented on GitHub (Oct 29, 2025):

@tainmar the list is real, but doesn't apply:

The list references QTSP status
This status is not required for eIDAS Level 1
It is required for eIDAS Level 2+3 which we don't offer yet
We will offer them medium term via partners
And longterm become a QTSP

Short-Term we don't need to be on that list to offer eiDAS Level 1 (SES) compliant signatures.

@ElTimuro commented on GitHub (Oct 29, 2025): @tainmar the list is real, but doesn't apply: - The list references [QTSP](https://en.wikipedia.org/wiki/Trust_service_provider) status - This status is not required for eIDAS Level 1 - It is required for eIDAS Level 2+3 which we don't offer yet - We will offer them medium term via partners - And longterm become a QTSP Short-Term we don't need to be on that list to offer eiDAS Level 1 (SES) compliant signatures.

kerem referenced this issue

2026-02-26 19:31:44 +03:00

[PR #612] [MERGED] chore: Improved the issue templates with issue forms (supported viayml ), closes #611 #1076

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#611

No description provided.

Rows
Columns