You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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':
Thank you for considering this feature request.
- Damian Ryse
The text was updated successfully, but these errors were encountered: