For some reason, the IssuerName parameter cannot be read when validating the signature, although the digital signature an authorized provider issues it, so the validation fails.
However, the private field m_distinguishedNameCollection contains the name (
CertDigital QUALIFIED CA G3
)
[0]"
{[C=RO,O=Centrul de Calcul S.A.,OU=CertDigital QUALIFIED CA G3,2.5.4.97=VATRO-2163993, System.Collections.Generic.Dictionary`2[System.String,System.String]]}"
[1] "{[CN=COSMIN-MATEI MACANEATA,SURNAME=MACANEATA,GIVENNAME=COSMIN-MATEI,SERIALNUMBER=201104209CMM11,[email protected],L=BUCURESTI SECTORUL 2,ST=BUCURESTI,C=RO, System.Collections.Generic.Dictionary`2[System.String,System.String]]}"
Looking forward to the news.
Thank you in advance!
Hi Dana,
Greetings from Syncfusion support.
Before we proceed with further validation, we kindly request clarification on whether you are using the EJ1 Signature control or the EJ2 Signature component. To assist you more effectively, we have provided the user guide documentation for both components.
EJ1 Signature – Documentation : https://help.syncfusion.com/angular/signature/getting-started
EJ2 Signature – Documentation : https://ej2.syncfusion.com/angular/documentation/signature/getting-started
Additionally, could you please specify whether you are attempting to include the signature inside the PDF component or the DocumentEditor component? Providing exact details about the component and platforms involved will greatly assist us in validating your query thoroughly and delivering a prompt solution.
Regards,
Suresh.
Hello,
Sorry, my mistake.
I chose the wrong platform.
Is for validating digital signatures on pdf's.
using Syncfusion.Pdf.Parsing;
PdfLoadedSignatureField signatureField = field as PdfLoadedSignatureField;
We have analyzed the reported issue and currently we are validating on this. We will update the further details by 22nd November, 2023.
We confirmed the issue “The issuer name details do not get properly from an existing signature field” as a defect in our product and we will include the fix into our upcoming weekly NuGet release, which will be available on December 5th, 2023.
Please use the below feedback link to track the status of the reported bug.
Note: If you require a patch for the reported issue in any of our Essential Studio Main or SP release version, then kindly let us know the version, so that we can provide a patch in that version based on our SLA policy.
Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”