@Mahesh_Gunaje You can use AEM Asset http API's to upload assets and use token based authentication to generate access token to allow 3rd application access to AEM HTTP API'shttps://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/authentication/overview.htm...
@JakeCham Please use below link to download latest version of dispatcher 4.3.6 as software distribution portal does not have the latest versionhttps://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/getting-started/release-notes.html?lang=en#downloads
@Anilkumar9 Can you check if you are already running an AEM instance on port 4502 or if any other process is using port 4502If yes, try to kill the process and then try
@akash_mca2008 Can you try purging cache using below format instead of using soft purgecurl -X PURGE -H 'x-aem-purge-key: PURGE_KEY' https://domain/url.html
@SDusane You can use sling model to fetch the groups associated with the user and check if user is part of the required group.Then you can show/hide html elements conditionally in navigation bar by calling that sling model in sightly code using use API
@HenryLiang Make sure you have system user created in Publisher and it has required permissions to assetsYou will not need authentication to call servlet in publisher. You can use postman to test this
@Kamaraj_AEM You can use content copy tool to copy content between environments in AEM CloudPlease find the below link for reference https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developer-tools/content-copy.html?lang=en
@Mahesh_Gunaje One of the use cases here would be to check authentication.For certain pages which needed authentication, sling filters can be used to check if user is logged in or else redirect to login page