When a user runs an SP (SAML Service Provider) web application in the environment where RH-SSO SAML adapter is installed on EAP 7.0 and the user customizes the session cookie name of the application (without using the default JSESSIONID), the customized session cookie name is not effective (not used) in the actual HTTP request/response headers.

A new session is created using HttpServletRequest#getSession(true) in the application if there is no current session. Also, the customization is to be done using <session-config><cookie-config><name> in web.xml like below.

     <session-config>
          <cookie-config>
              <name>MYSESSIONID</name>
          </cookie-config>
      </session-config>

The user wants to use the customized session cookie name in the SP application.