PDF Viewer component not visible on the page (6.5 version) | Community
Skip to main content
Best answer by AmitVishwakarma

Hi @_anon_ymous_ ,

Root Cause Possibilities:

1. Missing clientId for Adobe PDF Embed API
2. Incorrect Context-Aware Config (CAConfig) path
3. Core Components version incompatible
4. PDF URL not set or invalid
5. Browser blocking insecure content (HTTP PDFs on HTTPS site)
6. Missing Dispatcher Rewrite Rules (if applicable)

1. Check Client ID Configuration

Based on your screenshot, clientId is present: 28b07c6be4d544f...
Ensure this is from Adobe’s PDF Embed API registration: Get clientId

2. Correct Context-Aware Configuration (CAConfig)

Make sure the PDF Viewer component is inheriting the config.
Your configuration should be under:

/conf/<your-site>/settings/wcm/core/components/pdfviewer/v1/pdfviewer

Ensure the page where you’re placing the PDF viewer has CAConfig properly set in Page Properties > Advanced > Context-aware Configuration Path pointing to /conf/<your-site>.

 

3. Core Components Compatibility

Your AEM 6.5 must have Core Components 2.12.0+.
Verify installed version:

http://localhost:4502/system/console/bundles/com.adobe.cq.core.wcm.components.core

Upgrade if needed: Download Core Components

3 replies

MonalikaKapoor
Adobe Employee
MonalikaKapoorAdobe Employee
Adobe Employee
March 18, 2025

Hi @_anon_ymous_,

Could you please ensure that the PDF Viewer component version you are using is compatible with AEM 6.5. According to the PDF Viewer Component documentation, the component should be compatible with AEM 6.5. Make sure that your AEM instance has the necessary version of the Core Components installed.

 

    _
    _Anon_ymous_Author
    March 27, 2025

    Hi @monalikakapoor ,

    I’ve received the trial client ID, and the PDF Viewer is working, but I’m noticing that some features like download, print, dock, and undock are not functional.

    Can anyone confirm if the PDF Viewer trial provides access to only a limited set of features, or is there something else I might need to enable these options?

     

     

    Thanks in advance!

     

    giuseppebaglio
    giuseppebaglio
    Level 10
    March 18, 2025

    hi @_anon_ymous_, have you checked if the component requirements are satisfied? Please take a look at the "Context Aware Config" section of its documentation:

    clientId - Required - the client key obtained by registering for the view sdk api - https://www.adobe.com/go/dcsdks_credentials
      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity AdvisorAccepted solution
      Community Advisor
      March 18, 2025

      Hi @_anon_ymous_ ,

      Root Cause Possibilities:

      1. Missing clientId for Adobe PDF Embed API
      2. Incorrect Context-Aware Config (CAConfig) path
      3. Core Components version incompatible
      4. PDF URL not set or invalid
      5. Browser blocking insecure content (HTTP PDFs on HTTPS site)
      6. Missing Dispatcher Rewrite Rules (if applicable)

      1. Check Client ID Configuration

      Based on your screenshot, clientId is present: 28b07c6be4d544f...
      Ensure this is from Adobe’s PDF Embed API registration: Get clientId

      2. Correct Context-Aware Configuration (CAConfig)

      Make sure the PDF Viewer component is inheriting the config.
      Your configuration should be under:

      /conf/<your-site>/settings/wcm/core/components/pdfviewer/v1/pdfviewer

      Ensure the page where you’re placing the PDF viewer has CAConfig properly set in Page Properties > Advanced > Context-aware Configuration Path pointing to /conf/<your-site>.

       

      3. Core Components Compatibility

      Your AEM 6.5 must have Core Components 2.12.0+.
      Verify installed version:

      http://localhost:4502/system/console/bundles/com.adobe.cq.core.wcm.components.core

      Upgrade if needed: Download Core Components

        Terms & ConditionsAccessibility statement

        Loading footer...