Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] User owned certificate per signing #362

Open
DamianRyse opened this issue Sep 18, 2024 · 0 comments
Open

[Feature Request] User owned certificate per signing #362

DamianRyse opened this issue Sep 18, 2024 · 0 comments

Comments

@DamianRyse
Copy link

Hello,
I'm really missing the possibility for users to use their own PFX certificate when signing a document. Comparing to Adobe Reader, I can sign the document and also use my own digital ID (certificate) to validate my signing.

At the moment in DocuSeal, the application embeds a server-owned certificate after signing into the document which covers all signings. This does prevent the document from altering but does not prove that the signings are valid.

My suggestions would be':

  • When users signing a document, they can optionally provide a PFX certificate.
  • When no user-owned PFX certificate has been provided, the server-owned certificate must be used.
  • When a certificate is uploaded to DocuSeal (in the app settings) and named as an e-mail address, it should be defaulted to the signer using that e-mail address - but with entering the PFX passphrase for additional security and validation.
    • ALTERNATIVE: For registered users, they can upload their own PFX certificate to their user profile.

Thank you for considering this feature request.
- Damian Ryse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant