Forum Discussion
NimbostratusProblem with cookie persistance - iNotes
Hi all, i'm following the F5 doc with iNotes (i have v11.5.0 HFA4 installed) and seems that i'm struggling with the cookie persistance when switching to different node. The problem i see right now is that VS by default attaches cookie (ex. pool name /SHARED/p_TEST): BIGipServer~SHARED~p_TEST_http and from the iRule i'm setting the cookie like (HTTP::cookie insert name BIPipServer[LB::server pool] which inserts the cookie like: BIGipServer/SHARED/p_TEST_http and the persistance is not working (the old server is called instead of the new one). I have tried also to use my own cookie name but when i'm doing: HTTP::cookie insert name TEST_iNotes value $pcookie path "/" persist add uie [HTTP::cookie "TEST_iNotes"] then both LB nodes are selected the next time the client is back with query.
Any help with this would be nice.
To describe the problem: At first all clients are authenticating on the cluster (2 servers) and after auth they stay on it (if they mailbox is there) or should be redirected to some other node (i'm asking the Notes server for the client mailbox location and back i'm receiving the host name which then i'm translating to IP). Many thanks for any help.
3 Replies
Darek_H_152835Ok - i have solved this /SHARED/TEST with replacing it with ~ (why it's like that by default name in the cookie - don't know).
- Darek_H_152835
I have gone into new problem - how the persistence cookie is encrypted by default (i have read that it is AES 192 with base64 encoding) but i can't achieve the same results using the iRule. I'm trying right now:
b64encode [AES::encrypt $::key $cookie]
but this produces different results as the one that are build into the profile or cookie persistence. Any hints ?
- Darek_H_152835
To clarify the situation with the manually cookie encoding vs persistence cookie encoding. During the Notes work i have to change the node when the mailbox is on different server. As the persistence is based on the cookie (would like to encrypt it) i have also to change the cookie itself. When it's not encrypted - everything is working ok. When i enable the encryption then VS don't recognize my encrypted cookie correctly and ... places back his own cookie (old one).
I have tried both encryptions:
b64encode [AES::encrypt $::key $cookie]
HTTP::cookie encrypt $cookie $::key "192"
Neither of this above is producing a result that VS correctly decodes. Have anyone tried to replace the Profile encrypted cookie with it's own ?
