Forum Discussion
Chris_Miller
Altostratus
Feb 21, 2011Default Cookie Name Behavior
I'm load balancing an application behind IBM's WebSEAL product. A User authenticates via WebSEAL which then sends the traffic to the application VIP. According to the link below, WebSEAL adds a prefix to cookie names. So, rather than seeing a cookie named "BIGipServer," I see "AMWEBJCT!BIGipServer*"
http://publib.boulder.ibm.com/infoc...min180.htm
I'm wondering what LTM will do if it receives this as the cookie name? Will it see that the name contains BIGip and do its job, or is it looking for the exact name?
- hoolio
Cirrostratus
Hi Chris,http://devcentral.f5.com/wiki/default.aspx/iRules/http__cookie Rename a cookie by inserting a new cookie name with the same value as the original. Then remove the old cookie. when HTTP_REQUEST { Check if old cookie exists in request if { [HTTP::cookie exists "old-cookie-name"] } { Insert a new cookie with the new name and old cookie's value HTTP::cookie insert name "new-cookie-name" value [HTTP::cookie value "old-cookie-name"] Remove the old cookie HTTP::cookie remove "old-cookie-name" } }
- Chris_Miller
Altostratus
Aaron - the flow is like this: Client -> VIP -> WebSEAL Pool member -> VIP -> WebLogic Pool Member - Chris_Miller
Altostratus
Good news Aaron. I thought about this more and got to wondering whether WebSEAL was only renaming the cookie between itself and the client. As it turns out, that is indeed the case. When WebSEAL sends the request to the WebLogic VIP, it does so without the junction name so LTM sees the original BIGip cookie. I used an excellent example of yours to log all cookie names to confirm.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects