Hi @KotiReddyNa,Let me clarify:Technical Accounts created under the integration tab of an AEM instance's Developer Console do not expire.However, the certificate (credentials) under a technical account expires by default after one year. And you are right, you can generate a new certificate when the ...

Hi @monish_gavali_23, Checking this thread [1], it looks like AEM does not support the client_credentials flow, i.e., 2-legged authentication but the thread seems to be quite old so I am not sure if there have been any updates since. [1] - https://experienceleaguecommunities.adobe.com/t5/adobe-exper...

Hi @naruk89179065,For Integration (Technical) accounts setup in an AEM Cloud author environment's Developer Console, Oauth is not supported yet and it still relies on JWT for authentication. You can refer this thread for more details and links for relevant documentation: https://experienceleaguecomm...

Hi @SrinivasC1, Further adding to the documentation shared by @arunpatidar, if you're not able to see your templates in the page creation wizard, please ensure the below steps are complete:Enable the TemplateBefore a template can be used, it must be enabled by either:Enabling the template from the T...

Hi @KumariSu, I believe you can overlay the nodes under /libs/wcm/core/content/sites/jcr:content/rails/timeline/items/timeline/items/events/providers/activities/titles for your needs. Hope this helps,Vinay

It is recommended to upgrade to the latest AEM SP whenever possible but you could try to downgrade the archetype version in the project generation command as a temporary workaround. Archetype versions - [18-23] should be compatible with AEM version 6.5.0 Here's a table of the archetype versions and ...

Hi @pruthvira, There seems to be a requirement mismatch between the AEM version in your maven command - aemVersion="6.5.0" and the Adobe Experience Manager Core WCM Components Core Bundle (com.adobe.cq.core.wcm.components.core) deployed in your instance - "2.17.12". Checking this documentation: http...

Given that the integration accounts use JWT based authentication, a PKCS8 encoded private key would be necessary to facilitate the authentication process. Here's a blog post that covers end-to-end implementation instructions on how to use the service credentials for authorizing access to an AEM Clou...

Hi @Abhijeet_Kumar, For Integration (Technical) accounts setup in an AEM Cloud environment, Oauth is not supported and it relies on JWT for authentication. From Adobe's official documentation: "The AEM Developer Console (note the AEM in the name, which distinguishes it from the Adobe Developer Conso...