Forbidden api cf picker in Component | Community
Skip to main content
dante8888
dante8888
February 5, 2025
Solved

Forbidden api cf picker in Component

  • February 5, 2025
  • 2 replies
  • 599 views

I have an issue with sling:resourceType="dam/cfm/components/cfpicker" in AEMaaCS.

I am now getting a 403 Forbidden error when trying to reopen the dialog again.

Previously, it was working fine.

API: /mnt/overlay/dam/cfm/content/cfpicker/picker.html

Please let me know if you have any suggestions. Thanks!

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 dante8888

Yes, I switched to using another resource type: granite/ui/components/coral/foundation/form/pathfield.
As Adobe Support suggested, we need to add permission to /libs for dam/cfm/components/cfpicker, but this comes with some risk.

2 replies

Avinash_Gupta_
Community Advisor and Adobe Champion
Avinash_Gupta_Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 5, 2025

Hi @dante8888 ,

 

Have you checked for the errors on the log file? Found a related post to the similar kind of issue:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-core-content-fragment-component-cf-picker-on-the-dialog-is/m-p/590563 

 

Hope this may help.

 

Thanks,

Avinash

    dante8888
    dante8888Author
    February 5, 2025

    Yes, I already checked, but I used OOTB function, my server returned 403, it’s differential

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    July 14, 2025

    @dante8888 Just checking in — were you able to resolve your issue?
    We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

    Kautuk Sahni
    dante8888
    dante8888AuthorAccepted solution
    July 15, 2025

    Yes, I switched to using another resource type: granite/ui/components/coral/foundation/form/pathfield.
    As Adobe Support suggested, we need to add permission to /libs for dam/cfm/components/cfpicker, but this comes with some risk.

      Terms & ConditionsAccessibility statement

      Loading footer...