We are designing an application in AEM 5.6.1 that would utilize user sessions, and noticed that sessions are disabled in global.jsp. Concerns about statelessness aside, why does global.jsp include session="false" in the page directive? What consequences, if any, should we expect if we remove that and start using sessions in some components?
Solved! Go to Solution.
It is big topic. In short not encouraged to use httpsession an simple example it breaks caching at dispatcher and many more.
Views
Replies
Total Likes
It is big topic. In short not encouraged to use httpsession an simple example it breaks caching at dispatcher and many more.
Views
Replies
Total Likes
Sham HC wrote...
It is big topic. In short not encouraged to use httpsession an simple example it breaks caching at dispatcher and many more.
Thanks for the reply. What would you recommend then as the way to track a customer's authentication?
Views
Replies
Total Likes
bsstephan wrote...
Thanks for the reply. What would you recommend then as the way to track a customer's authentication?
One of option is clientcontext http://docs.adobe.com/docs/en/cq/current/administering/client_context.html
Do AEM and the JCR support having thousands of customers being created as users if we were to use the Adobe Granite SAML handler for customers?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies