Thanks Joerg for your feedback. I have created now a Daycare ticket for the missing documentation.According to the "pure" OSGi Installer approach, I thought more of uploading the package or bundle directly to the "install" folder/node below /apps in the JCR repository, so not the install folder in t...

Hi Vish.dhaliwal​thanks for response. Yes I'm aware of the content-package-maven-plugin.I think actually too, that the usage of the CRX HTTP API is like the more structured way.But I have heard once at some AEM/Sling Conference, that the installation handling via the OSGi Installer is much more stab...

Hi,I would like to automate a bit the deployment of CRX/Vault packages to AEM instances. As of now I know about these two possibilities:- CRX HTTP Service API: Using cURL or some other tool to upload/install/uninstall/etc. packages via CRX- Sling OSGi Installer: Simply uploading bundles or vault pac...

Ahh interesting - because as I did the same procedure as you described, I did not receive a config node name with a Dash in between the Factory PID name and Identifier...which AEM version did you use?

Ahh so we have found now the solution: We needed to rename the config xml file to "com.adobe.granite.cors.impl.CORSPolicyImpl-IDENTIFIER.xml".So we needed to add a Dash between the Factory PID and the IDENTIFIER.Before we added manually via the Felix Config console the additional config and then we ...

As you can see JaideepBrar​ in my previous comment with the Screenshot, we used actually the same PID ("com.adobe.granite.cors.impl.CORSPolicyImpl.c9d2e058-2403-43ac-8755-a5693ddf4ae8")...that's why we are a bit confused....

Hi JaideepBrar​,sorry need to correct my initial description: The configuration worked so far for one added custom configuration, but it is displayed not right below the "Adobe Granite Cross-Origin Resource Sharing Policy" in the Felix Configuration view, which was a bit confusing.Screenshot:

We tried to update our CORS configuration in AEM 6.5.0.0 according to this help article: Adobe Experience Manager Help | Understanding Cross-Origin Resource Sharing (CORS) with AEM .But this does not seem to work (anymore). If we follow the guide and add it to your package and deploy it again. It do...

Hi @kautuksahni,I have done this, but then the AEM instance is not available anymore, also not via the SSL configured port as I have already mentioned in my initial question.I have checked this on a vanilla AEM instance.

Hi @sureshr19072451,it is recommended to set a new Password for the "replication-receiver" user. You can do this by simply login as admin and change the password of this user.