[PDF] Need different PdfViewerCaConfig on publish

[rzasap]

PDFViewer component needs context aware config com.adobe.cq.wcm.core.components.internal.services.pdfviewer.PdfViewerCaConfig which varies per domain.
As stated in Adobe Document Services documentation: "Your Credentials is restricted to the domain you enter here, plus any subdomains. It is recommended that you create a separate Credentials for each sub-domain." - so we need different configurations for the author and for the publish.

Let's suppose that we have multiple sites with different domains. We also want the PDFViewer component to work on the author.

Here is example content structure:

/content/my-project/siteA
/content/my-project/siteB 
/content/my-project/siteC
... 

and corresponding configuration:

/conf/my-project/siteA
/conf/my-project/siteB
/conf/my-project/siteC
...

On /content/my-project/siteA we set sling:configRef to /conf/my-project/siteA and simmilary on /content/my-project/siteB.
We have added the required configuration for the author domain on the author instance.

Now everything works fine on the author, but on publish I need to have different configurations.
Do I need to go to every publish and change it? This sounds rather troublesome.
Ideally, I would like to be able to edit the configuration on the author and replicate the changes to all publish instances.

We have thought of setting different sling:configRef at /content/my-project/siteA on author (/conf/my-project.author/siteA) and different on publish (/conf/my-project.publish/siteA) but this is not ideal either, because it can be overriden when author activate the /content/my-project/siteA.

Do you gays have some recommendations for keeping and maintaining such configuration?

[jckautzmann]

Now everything works fine on the author, but on publish I need to have different configurations.

Why would you have different configurations on publish? Could you please elaborate?

[rzasap]

Let's suppose we have domains like this:

author -> author.my-project.com
publish, site A -> sitea.com
publish, site B -> siteb.com

According to Adobe Document Services we need a separate configuration per domain.

If I use the config from author -> author.my-project.com then PDF Viewer component does not work, because it is used on
the site with a different domain.

[ky940819]

I haven't tested it but I think you can use the OSGI configuration Apache Sling Context-Aware Configuration Override Provider: OSGi configuration

Make a configuration for this and scope that configuration to author runmode.

[rzasap]

Thanks @ky940819,
I will definitely test it and give you feedback. Maybe is it worth mentioning it in component documentation?

[jckautzmann]

We discussed this topic internally. One solution would be to introduce a specific PdfViewerCaConfigPublish configuration for the publish instance which falls back to PdfViewerCaConfig (configuration for the author instance) if not set. The logic in PdfViewerImpl would take the configuration based on the run mode (author/publish).

[rzasap]

Thanks @jckautzmann ,
I will wait for the changes 👍
I have also tested proposed by @ky940819 workaround and it seems to work fine for a now.