Enabling sessions for use in the publicly-facing site

[bsstephan]

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?

[Sham_HC · Accepted solution]

It is big topic. In short not encouraged to use httpsession an simple example it breaks caching at dispatcher and many more.  

[bsstephan]

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?

[Sham_HC]

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

[bsstephan]

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?