JSESSIONID cookie generation, security

Question

We have AEM deployed on JBoss server. Referring to existing forum links we got information that every JSP script should have following directive to avoid JSESSIONID cookie generation

<%@page session="false">

I was able to reproduce this behavior on a local non-server based AEM installation on geometrixx sample site (where removing above directive from jsp generated JSESSIONID cookie, adding didn't generate).

But on our application on AEM running on JBoss, we had a template with sightly, not including any JSP scripts (just to ensure, removed everything from page.html template file and had only sample message, to avoid including anything). When we access the page, AEM still generated JSESSIONID and its non-secured. This is being raised as security issue.

One option is to run AEM on SSL, another option per this reference link, we thought of changing only session cookie to secure. But the reference link is about Felix Jetty Service, which is not available in case AEM on JBoss server installation.

But when page template is not having any JSP script, JSESSIONID should not generate in first place. Any insights to this would be helpful.

Thanks,
Sandeep

WasilZee · Accepted Answer

AEM/Sling when deployed on web container, uses servlet bridge(felix http proxy). You should better disable the JSESSIONID on JBoss[2]. Also check out article[3][4]

Thanks,

Wasil

[1] Apache Felix - Apache Felix HTTP Service

[2] How do I remove the jsessionid from URLs in JBoss EAP? - Red Hat Customer Portal

[3] How to enable HttpOnly and Secure Session Cookies in EAP 6.x - Red Hat Customer Portal

[4] Configure domain of JSESSIONID cookie on JBoss - Red Hat Customer Portal