DocAssurance Service for encrypting PDF | Community
Skip to main content
A
Ashar97
Level 2
October 5, 2021
Solved

DocAssurance Service for encrypting PDF

  • October 5, 2021
  • 1 reply
  • 5842 views

Hello team,

 

I am trying to utilize the DocAssuranceService to encrypt PDFs. I have created a class using the Sample 1 under the Securing Documents section here:
https://experienceleague.adobe.com/docs/experience-manager-64/forms/use-document-services/aem-document-services-programmatically.html?lang=en#securing-documents

 

Additionally, I have a servlet identical to the below link, which calls the above class in order to retrieve a certified PDF.

https://experienceleague.adobe.com/docs/experience-manager-learn/forms/creating-your-first-osgi-bundle/create-servlet.html?lang=en

 

I have put a snippet of the class I have created to use the DocAssurance.

 

 

 

public class PassEncryptCertifyExtend { @3214626 private DocAssuranceService docAssuranceService; @3214626 private SlingRepository slingRepository; @3214626 private ResourceResolverFactory jcrResourceResolverFactory ; /** * * @90521 inputFile - path to the pdf document stored at disk * @90521 outputFile - path to the pdf document where the output needs to be stored * @throws Exception */ Document outDoc; Logger logger = Logger.getLogger("classname"); public Document SecureDocument(Document inDoc) throws Exception{ try { logger.info("***** CALLING ENCRYPTION OPTIONS *****"); outDoc = null; outDoc = docAssuranceService.secureDocument(inDoc, getPassEncryptionOptions(), null, null, null); logger.info("***** EXITING ENCRYPTION OPTIONS *****"); } catch(Exception e) { logger.error(e); } return outDoc; }

 

 

 

 
outDoc = docAssuranceService.secureDocument(inDoc, getPassEncryptionOptions(), null, null, null);

 

This line is providing a nullpointer exception when run. I can verify that the inDoc being passed is without any issues. In addition, thegetPassEncryptionOptions() method is being run successfully. I have tried various options such as just passing inDoc with other parameters as null, passing in with all other parameters, yet all variations return a nullPointer exception. The logger indicating the exit of the docAssuranceService.secureDocument does not run and the code returns back to the servlet. I was wondering if I could receive any guidance in this regard.

 

Error:

05.10.2021 15:30:09.987 *INFO* [0:0:0:0:0:0:0:1 [1633462209985] POST /bin/mergedataWithAcroform HTTP/1.1] classname ***** CALLING ENCRYPTION OPTIONS *****

05.10.2021 15:30:10.007 *ERROR* [0:0:0:0:0:0:0:1 [1633462209985] POST /bin/mergedataWithAcroform HTTP/1.1] classname java.lang.NullPointerException

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by workflowuser

    public InputStream certifyDocument(com.adobe.aemfd.docmanager.Document documentToCertify, String credentialAlias,
    String fieldName) {
    this.credentialAlias = credentialAlias;
    this.fieldName = fieldName;
    ResourceResolver resourceResolver = null;
    com.adobe.aemfd.docmanager.Document certifiedDocument = null;

    try {

    try {
    resourceResolver = getResolver.getFormsServiceResolver();


    certifiedDocument = docAssuranceService.secureDocument(documentToCertify, null,
    getCertificationOptions(resourceResolver), null, null);
    log.info("Certified the document");
    System.out.println("Certified document");
    certifiedDocument.copyToFile(new File("c:\\scrap\\abc.pdf"));
    } catch (Exception e) {
    e.printStackTrace();
    }

    } finally {


    try {
    return certifiedDocument.getInputStream();
    } catch (IOException e) {
    // TODO Auto-generated catch block
    e.printStackTrace();
    }
    }
    return null;
    }

     

    you can get the sample resolver from this link. You will have to deploy the bundle and add the user mapper settings as shown in the document

    1 reply

    W
    Adobe Employee
    workflowuserAdobe EmployeeAccepted solution
    Adobe Employee
    October 6, 2021

    public InputStream certifyDocument(com.adobe.aemfd.docmanager.Document documentToCertify, String credentialAlias,
    String fieldName) {
    this.credentialAlias = credentialAlias;
    this.fieldName = fieldName;
    ResourceResolver resourceResolver = null;
    com.adobe.aemfd.docmanager.Document certifiedDocument = null;

    try {

    try {
    resourceResolver = getResolver.getFormsServiceResolver();


    certifiedDocument = docAssuranceService.secureDocument(documentToCertify, null,
    getCertificationOptions(resourceResolver), null, null);
    log.info("Certified the document");
    System.out.println("Certified document");
    certifiedDocument.copyToFile(new File("c:\\scrap\\abc.pdf"));
    } catch (Exception e) {
    e.printStackTrace();
    }

    } finally {


    try {
    return certifiedDocument.getInputStream();
    } catch (IOException e) {
    // TODO Auto-generated catch block
    e.printStackTrace();
    }
    }
    return null;
    }

     

    you can get the sample resolver from this link. You will have to deploy the bundle and add the user mapper settings as shown in the document

      W
      Adobe Employee
      workflowuserAdobe Employee
      Adobe Employee
      October 6, 2021

      This article should also help you in certifying documents

        G
        GirishBedekar
        Level 8
        October 8, 2021

        Thanks for your comment - unfortunately it still does not pick it up. I had a colleague try as well and they experienced the same problem. Unsure if this jar is correct.
        The general idea is to use ResourceResolver to obtain the service user somehow. In this case, by 

         resourceResolver = getResolver.getFormsServiceResolver(); 

         

        There has been other ways to utilize such as here :

        ResourceResolver resourceResolver = null;
         try {

              /** resourceResolver with admin privileges to be passed to SignatureServiceAPI and Reader Extensions
              the resource resolver for signature options has to be corresponding to the user who has the signing certificate in his granite key store
              the resource resolver for signature options has to be corresponding to the user who has the credential for reader extension in his granite key store
              here we are using the same resource resolver
              */
              adminSession = slingRepository.loginAdministrative(null);
              resourceResolver = jcrResourceResolverFactory.getResourceResolver(adminSession);

              VerificationTime verificationTime = getVerificationTimeForPades();
              ValidationPreferences dssPrefs = getValidationPreferences();

              //retrieve specifications for each of the services, you may pass null if you don't want to use that service
              //for encrypted document pass Unlock Options - see the method getUnlockOptions() below
               outDoc = docAssuranceService.applyDocumentTimeStamp(inDoc, verificationTime, dssPrefs, resourceResolver, null);
         }
         finally{
             /**
              * always close the PDFDocument object after your processing is done.
              */
             if(inDoc != null){
                 inDoc.close();
             }
             if(adminSession != null && adminSession.isLive()){
                 if(resourceResolver != null){
                     resourceResolver.close();
                 }
                 adminSession.logout();
             }
         }

         outDoc.copyToFile(outFile);

        but in this case, the jcrResourceResolverFactory has been depricated. Workarounds are similar but not able to give the same format. In addition, the slingRepository.loginAdministrative has deprecated and now have to use loginService.

        The main solution needed would be to use ResourceResolver to obtain the service user as mentioned here.
        Then use it when calling

        (documentToCertify, null, getCertificationOptions(resourceResolver), null, null);





        Did you add the folllwing in the user mapper configuration in configMgr?

        • DevelopingWithServiceUser.core:getformsresourceresolver=fd-service
          Terms & ConditionsAccessibility statement

          Loading footer...