Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

ALC-DSS-303-014 Subject name and the subject alt name missing.

Avatar

Level 1

I get the following result when using the certify operation on the SignatureService (SOAP)

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soapenv:Body>

      <soapenv:Fault>

         <faultcode>soapenv:Server.generalException</faultcode>

         <faultstring>Caused by: com.adobe.livecycle.signatures.client.types.exceptions.PDFOperationException: ALC-DSS-303-002 Could not certify Signature Field signing_slip[0].#subform[0].signature[0] (in the operation : certify)

Caused By: ALC-DSS-303-014 Subject name and the subject alt name missing. (in the operation : getSignerName); nested exception is:

  com.adobe.livecycle.signatures.client.types.exceptions.PDFOperationException: ALC-DSS-303-002 Could not certify Signature Field signing_slip[0].#subform[0].signature[0] (in the operation : certify)

Caused By: ALC-DSS-303-014 Subject name and the subject alt name missing. (in the operation : getSignerName)</faultstring>

         <detail>

            <faultData>

               <ns1:message xmlns:ns1="http://adobe.com/idp/services">ALC-DSS-303-002 Could not certify Signature Field signing_slip[0].#subform[0].signature[0] (in the operation : certify)

Caused By: ALC-DSS-303-014 Subject name and the subject alt name missing. (in the operation : getSignerName)</ns1:message>

            </faultData>

            <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">LP00350</ns2:hostname>

         </detail>

      </soapenv:Fault>

   </soapenv:Body>

</soapenv:Envelope>

The certificate used has already been used by an older version of our application. We are now using ES4 and calling the  SOAP services directly using Spring-WS. All the other operations work ok, including ReaderExtensions (Reader extensions uses a different certificate, of course).

Thank you.

1 Reply

Avatar

Level 1

Hi there. I just found that the problem was in the certificate I was using.  Thanks