Hi @Keerthi97 ,There are couple of things I can suggest here:-If for your requirement you can manage just to have a unique id for every time a component is dropped in a page- ex-  testcontainer-someUniqueId, then use this documentation. You can have a js code to manipulate the component just by sear...

Hi @juancarlos2022 ,Looking at the image, it seems like you have some customization in your base page properties which is making it disable. This could have been done intentionally within your project. This is not how AEM OOTB page properties looks like. I would recommend to verify each property on ...

Hi @sai_rama_krishn ,You can utilize CUG concept in order to achieve this. see this example - https://experienceleague.adobe.com/docs/experience-manager-learn/assets/advanced/closed-user-groups....Just this configuration will not help you to achieve this, you will have to write a custom authenticati...

Hi @SahrudayaB ,Here the client is your AEM instance and server is the webpack where you are accessing the same AEM content without the authoring capabilities.In the documentation you will see "proxy": "http://localhost:4502",which means we are proxying this AEM instance and rendering all the conten...

Hi @nav_rasamalla12 ,There is no additional step that needs to be done for translation.What are the properties that are not getting translated? There is a rules file which defines what all properties will be translated. Check the files under this folder and see if it helps -  /libs/settings/translat...

As you might already know, AEM Adobe integration is a two step process-Creating the IMS configuration - When you create "Adobe IMS Configurations" for AEM and Target integration, the values gets stored at /apps/system/config/com.adobe.granite.auth.oauth.accesstoken.provider.c023ae85-c724-46d5-8512-e...

Try restarting the server post all the configurations and the check if it works.

Hi @divanshug96 ,Please follow this documentation - https://aemsimplifiedbynikhil.wordpress.com/2021/12/01/apache-sling-sitemap-for-aem-6-5-11-and-aemaacs/ 

As you might already know, AEM Adobe integration is a two step process-Creating the IMS configuration - When you create "Adobe IMS Configurations" for AEM and Target integration, the values gets stored at /apps/system/config/com.adobe.granite.auth.oauth.accesstoken.provider.c023ae85-c724-46d5-8512-e...

refer this for the techniques to prevent sql injections - https://labs.tadigital.com/index.php/2018/11/05/sql-injections-overview-and-prevention-techniques/