@ranjitha29 "Request for Activation" workflow model is automatically triggered if the user clicking activate doesn't have replication privileges under the path. See here as well:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-1-request-for-activation-process/qaq-p/293...

The only ways to avoid the issue:1. Create a script to create the user nodes in AEM ahead of time2. Enable sticky sessions on the load balancer so the user is always sent to the same AEM instance.

As @Jörg_Hoh said, please file a support ticket. The saml response XML gets stored in encrypted form under the user node.  That xml isn't complying with the xmil structure that the createLogoutRequest method expects.  So we might need to do some debugging there.

SurendraKonatha.Once you get access then please let me know which ones you need, I will make sure they are published in the software distribution site for you and others to download.  Thanks,Andrew

I'm not sure, but it sounds like based on your description you are trying to serve a static HTML file via AEM?  Here is another forum post on the same thing:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/hosting-static-html-in-the-jcr/qaq-p/223359

@Albin_Issacif you look at the stack trace the the HashMap throwing the exception is from Apache Jackrabbit Oak code at org.apache.jackrabbit.oak.security.authorization.permission.PermissionEntryProviderImpl.loadEntries(PermissionEntryProviderImpl.java:163) [org.apache.jackrabbit.oak-core:1.8.7] I f...

What version of AEM is this?  What version of oak-core bundle do you see in /system/console/bundles?  I would like to contact Adobe Engineering team for this issue.  I suspect there is a product issue here. See the issue I filed here: https://issues.apache.org/jira/browse/OAK-9117

The likely reason the workflow would get aborted would be due to the payload being published/replicated, see this article: https://helpx.adobe.com/experience-manager/kb/workflow-is-getting-aborted-without-any-error-or-exception.html

Since there is no way to define which handler on the same path to trigger for authentication you would have to do some customization. You could implement a custom servlet /bin/auth and configure the authentication handlers under subpaths of the servlet - for example /bin/auth/saml.  When the user ac...

Here is the correct doc for 6.5:https://docs.adobe.com/content/help/en/experience-manager-65/administering/security/saml-2-0-authenticationhandler.html Sorry for the confusion with the 6.3 doc, I will notify our docs team.