I'm not sure if I'm able to understand your requirement correctly. In general, you can create specific AD groups per AEM app or some other logic based on your business use case(s) and add the users to each AD group who would get created in AEM and assigned to that same group. You would just need to ...
there are multiple ways to implement vanities, where/how did you create it? Did you use sling:vanity or sling:redirect?I just tested on a we-retail page via page properties(sling:vanityPath) and it shows in console as expected.On '/content/we-retail/us/en.html', I added '/content/we-retail/us/ca' as...
check /libs/dam/components/scene7/dynamicmedia/dynamicmedia_sly.js#470, you'd see that it requires 'imageserver' url/config and is configured to work in disabled mode470 - contentPath = imageServer.replace("/is/image", "/is/content");check if you've configured 'imageserverurl' property or otherwise ...
this is the latest release updated 3 months back and the code package seems to be fine except latest conventions like usage of static templates etc.You could test it in 6.4 if you've license keys or otherwise you may open a ticket @ https://github.com/coresecure/Adobe-AEM-Brightcove-Connector/issues...
Could you share more details about your use case? Are you trying to connect to AEM from SFDC app or vice versa?JDK1.8 is recommended for 6.4, minor versions won't matter.
https://demo.com/content/demo/us/en/_jcr_content/root/responsivegrid/responsivegrid_147183 1795/responsivegrid_165… to https://demo.com/content/demo/us/en/_jcr_content/root/responsivegrid/responsivegrid_147183 1795/responsivegrid_165…happens with "reverse_mapping_content_nohtml" per shared rules...
aem-groovy-console-12.0.0.zip @ https://github.com/icfnext/aem-groovy-console/releases delivers 2.4.13 which is compatible with 6.4At least groovy console works fine with this version.Give it a shot.