how to setup persistence to concatenate jvmRoute with JSESSIONID to generate final SESSIONID

do you mean concatenating jvmroute and jsessionid to be a persistence key? are you using universal persistence?

if yes, you can just put them together e.g. [HTTP::cookie "JSESSIONID"][HTTP::cookie "jvmRoute"].

sol7392: Overview of universal persistence

do you mean concatenating jvmroute and jsessionid to be a persistence key? are you using universal persistence?

if yes, you can just put them together e.g. [HTTP::cookie "JSESSIONID"][HTTP::cookie "jvmRoute"].

sol7392: Overview of universal persistence

Since jvmRoute is already appended to the JSESSIONID by Tomcat you can just consider it as part of the JSESSIONID. The irule in the linked page should work out of the box.

Note that setting the jvmRoute in Tomcat server.xml has no added value from a universal persistence perspective. It only appends a string to the JSESSIONID but does not make it more unique.

For one client I created an irule that only use the jvmRoute part of the JSESSIONID to select the backend. It probably as slightly more processing overhead but limits the number of entries in the session table. However, unless you have extreme numbers of current user sessions I would recommend using the example iRule from the page you referred to.

Hi All,

We have similar requirement i.e. to persist at BIG-IP level in this pattern "JSESSIONID.jvmRoute". I would like to know if this iRule below would help us in achieving that goal.

when HTTP_RESPONSE {
  if { [HTTP::cookie exists "JSESSIONID"] } {
   persist add uie [HTTP::cookie "JSESSIONID"][HTTP::cookie "jvmRoute"]
  }
}

when HTTP_REQUEST {
  if { [HTTP::cookie exists "JSESSIONID"] } {
    persist uie [HTTP::cookie "JSESSIONID"][HTTP::cookie "jvmRoute"]
  }
}

Regards, Ram

Hi All,

Along with above requirement, we would like to encrypt the Cookie content. So there is already a Profile under Persistence that we created to use HTTP Insert Cookie method and encrypt the Cookie content using a passphrase. I would like to know if it is okay to have a profile separately to encrypt along with this iRule or do we need to modify the iRule to have them together. Like, have JSESSIONID and encryption of Cookie content in a single iRule.

when HTTP_RESPONSE {
 if { [HTTP::cookie exists "JSESSIONID"] } {
   persist add uie [HTTP::cookie "JSESSIONID"]
  }
}

when HTTP_REQUEST {
  if { [HTTP::cookie exists "JSESSIONID"] } {
    persist uie [HTTP::cookie "JSESSIONID"]
  }
}

Regards, Ram

This is for encrypting Cookie content to improve security. It is a PCI requirement.

Hi Winston,

I was referring to this KB to encode the pool member information.

https://support.f5.com/csp/article/K23254150

IPv4
BIGipServer=..0000

IPv6
BIGipServer=.

During security audit we found out that our member pool information were in 'plain text' so we had to encrypt the Cookie.

Regards, Ram