Hi @arunpatidar Unfortunately, it doesn't answer my question regarding SAML integration using the AEM SAML Authentication Handler.If the SAML Authentication Handler is used for integration with IDP then I would also assume that should be able to handle SAML Logout Response triggered by IDP, especial...

I have the scenario that I have 2 sites site1.company.com and site2.company.com on AEM, both of them have protected pages (CUGs), and both of them are integrated with the same IDP using SAML Authentication Handler. SAML Authentication Handler is also set to handle logout.When a user logs in to one o...

Hi @Nitin_laad Sorry for late response but I wanted to try methods from the links. Unfortunatly I still see warning in the log connected to /oak:index/lucene What was done: after in place upgrade - remove "crx-quickstart/repository/index" and TarMK Offline indexing with oak-run.jar most of indexes i...

Hi @Nitin_laad I was executing checkConsistency(java.lang.String indexPath, boolean fullCheck) from "/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3DLucene+Index+statistics%2Ctype%3DLuceneIndex"Based on How to check and repair search index inconsistencies (adobe.com) could you please clarifi ...

Hi @Nitin_laadThanks for response but I have executed offline reindexation of this index and also online one by changing reindex property and still warning is showing up.

Hi,On AEM 6.5 SP 10 after upgrading it from 6.3 with in-place method from time to time I can see this type of WARN. The name of file changes  *WARN* [oak-lucene-69522] org.apache.jackrabbit.oak.plugins.index.lucene.IndexCopier File _11da_Lucene41_0.pos doesn't exist in PATH_TO_QUICKSTART/repository/...

Hi @Asutosh_Jena_Thanks for the update.This was not working for my container like you described and now I know why My custom container has a policy applied with allowed components which is wider than the policy created for accordion. It seems that when the component has its own policy then the acco...

Hi,I would like that this policy would only apply to the container inside the accordion (in the scope of the accordion policy) but not to the container outside the accordion. Is possible?

Hi @Asutosh_Jena_Thanks for your response.I'm aware of creating a policy for accordion so I can select only allowed components. But my question is related to using the policy for component one level down. - accordion_policy -- allowed components --- container  ---- allowed components ----- same comp...

Hi,I want to use the accordion component from core components but I don't want to nest it. The approach is that to create a policy that will not allow adding accordion to the accordion panels. I would like to add a possibility to add a container to the accordion panel but restrict this container to ...