Rules of AEM

Migrating from AEM 6.x to AEM as a Cloud Service: What to Expect ? Introduction If you're currently managing an AEM 6.x project, chances are you’ve heard about AEM as a Cloud Service (AEMaaCS). Adobe is clearly shifting toward this cloud-native model for low/medium complex customers and while there are definite benefits, developers should be prepared for a few surprises too. I recently worked on a migration project and wanted to share what developers should expect , from code refactoring and CI/CD changes to losing root access and dealing with strict dispatcher rules.     Whats is Great about AEMaaCS  1. Automatic Upgrades Say goodbye to manual patching. AEMaaCS updates automatically.  Adobe handles the platform updates, with no need to plan downtime or test service packs. 2. CI/CD with Cloud Manager Deployments go through Adobe Cloud Manager, which checks for code quality, security, and performance before pu...

  AEM - LDAP Integration LDAP (the   L ightweight   D irectory   A ccess   P rotocol) is used for accessing centralised directory services.  You can achieve below vital things with LDAP integration The User accounts can be synchronised between LDAP server and the AEM repository.  The AEM uses LDAP authentication  to authenticate users, with credentials being passed to the LDAP server for validation.  To improve performance, successfully validated credentials can be cached by repository, with an expire timeout. This helps reduce the effort required to manage user accounts as they can be accessed by the multiple applications.  When a user/account is removed from LDAP server validation is no longer granted & access to the AEM is denied.  The following are the AEM steps for integrating the LDAP and using it as your Single Sign On (SSO) source of truth for authenticating AEM Users. In order to have LDAP working with AEM, you need to ...