AEM 6.5: Adding custom Factory configuration for CORS does not work anymore | Community
Skip to main content
OlivBur
OlivBur
Level 2
May 14, 2019
Solved

AEM 6.5: Adding custom Factory configuration for CORS does not work anymore

  • May 14, 2019
  • 8 replies
  • 5979 views

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 does not recognize it as an instance of the CORS configuration factory component.

We have the same issue with adding a custom Logging to the LogFactory, as documented here: Monitoring and Maintaining Your AEM instance

Do you have the same issue? We haven't tested it yet with the latest AEM 6.4.x.

Thanks for support.

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 OlivBur

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 simply packaged up the stored config nodes from the CRX. But this procedure seems not to work for Factory configs.

Actually this is also documented here: Configuring OSGi in a special Note box .

8 replies

U
Adobe Employee
user05162Adobe Employee
Adobe Employee
May 14, 2019

As mentioned at [1], Setup the following logging to check why its failing:

Logging is available under com.adobe.granite.cors:

  • enable DEBUG to see details about why a CORS request was denied
  • enable TRACE to see details about all requests going through the CORS handler

[1] Adobe Experience Manager Help | Understanding Cross-Origin Resource Sharing (CORS) with AEM

OlivBur
OlivBurAuthor
Level 2
May 14, 2019

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:

U
Adobe Employee
user05162Adobe Employee
Adobe Employee
May 14, 2019

I believe you need to match the pid in order for it to show up under the CORS config. Check screenshot below:

OlivBur
OlivBurAuthor
Level 2
May 14, 2019

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....

OlivBur
OlivBurAuthorAccepted solution
Level 2
May 14, 2019

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 simply packaged up the stored config nodes from the CRX. But this procedure seems not to work for Factory configs.

Actually this is also documented here: Configuring OSGi in a special Note box .

    U
    Adobe Employee
    user05162Adobe Employee
    Adobe Employee
    May 14, 2019

    I tried editing the CORS configuration from /system/console/configMgr. Once i save the changes, noticed the following file getting created under crxde:

    /apps/system/config/com.adobe.granite.cors.impl.CORSPolicyImpl-122113ad-1f51-4b73-9c4f-ba1c0d2f1395.config

    Have you tried updating the configuration from /system/console/configMgr ?

    In another test, I installed the copy-pasted the "com.adobe.granite.cors.impl.CORSPolicyImpl-122113ad-1f51-4b73-9c4f-ba1c0d2f1395.config" and changed the PID and can see the configs under CORS:

    So, check the syntax as you should only be changing the PID number (122113ad-1f51-4b73-9c4f-ba1c0d2f1395) for example

    OlivBur
    OlivBurAuthor
    Level 2
    May 14, 2019

    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?

    M
    mohita82734067
    Level 2
    October 16, 2020

    @olivburHow did you fixed this problem for CORS configuration? We are facing the same issue when we add CORS config to package and deploy it again.

    Terms & ConditionsAccessibility statement

    Loading footer...