Can you share the stack trace from the error.log when you get this error in the browser ? Also, have you tried with admin user ?

Have you already gone through the docs at [1] and sample code at [2] [1]https://docs.adobe.com/content/help/en/experience-manager-learn/foundation/authentication/oauth-code-sample-develop.htmlhttps://labs.tadigital.com/index.php/2017/08/18/aem-as-oauth-server-part-1-setting-up-scopes/ [2]https://git...

The latest Archetypes automatically embeds the latest release of core components. That will be the recommended approach for having consistency across environments. See below[1] [1] https://docs.adobe.com/content/help/en/experience-manager-learn/getting-started-wknd-tutorial-develop/project-setup.htm...

Right now, the functionality you are looking for does not exist OOTB and you will need to create custom listeners which listen to the deactivation event and proceed as per your business requirement.

This is configured at [1] under "Async Indexer Configs" [1] http://<host>:<port>/system/console/configMgr/org.apache.jackrabbit.oak.plugins.index.AsyncIndexerService

Incremental indexing runs every 5 seconds in the background. you can setup a DEBUG logger on the following classes to validate that: org.apache.jackrabbit.oak.plugins.index

If you have enabled AEM to save audit data, you can query the nodes under "/var/audit/com.day.cq.wcm.core.page/content" Nodetypes : cq:AuditEventProperty: cq:type=PageDeleted

Truststore was moved to a global location at  http:/serveraddress:serverport/libs/granite/security/content/truststore.html More details at [1] [1] https://docs.adobe.com/content/help/en/experience-manager-64/administering/security/saml-2-0-authenticationhandler.html#add-the-idp-certificate-to-the-ae...

1) You can look into using CUG's[1] to restrict the access2) By default, any page that needs a login token is not cached but if you still want to cache it, you can use the /allowauthorized=13) Yes, you can create multipe for SAML based on the path attribute. [1] https://docs.adobe.com/content/help/e...

The best way to know the root cause of this issue is to go to OSGI installer after you deploy the configuration and check the state of that config. There might be conflict with other configurations Or the config file under crx-quickstart/launchpad/config/**** might not be owned by crx user. [1] http...