Enabling sessions for use in the publicly-facing site | Community
Skip to main content
B
bsstephan
October 16, 2015
Solved

Enabling sessions for use in the publicly-facing site

  • October 16, 2015
  • 4 replies
  • 848 views

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?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Sham_HC

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

    4 replies

    Sham_HC
    Sham_HCAccepted solution
    Level 10
    October 16, 2015

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

    B
    bsstephanAuthor
    October 16, 2015

    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
    Sham_HC
    Level 10
    October 16, 2015

    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

      B
      bsstephanAuthor
      October 16, 2015

      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?

      Terms & ConditionsAccessibility statement

      Loading footer...