Forum Discussion
boneyard
MVP
Mar 10, 2013ssl::renegotiate changes SSL session ID and makes it impossible to resume?
when calling ssl::renegotiate (in v11.2 / 11.3) it seems that the SSL session ID changes (very slightly, gets +1 somewhere near 2/3s) and can't be used anymore by new resume requests that request in ...
Kevin_Stewart
Employee
Mar 10, 2013When you call SSL::renegotiate, do you also by chance call SSL::authenticate with a value of "always", or not call it at all?
I've noticed that if you have the frequency set to "once" in the client SSL profile (the default setting), and you don't specify 'once' in your iRule, it will (sort of) behave as if always was selected (as in not storing session IDs across TCP sessions). In my testing, with 'SSL::authenticate once' in the iRule just before 'SSL::renegotiate', upon the server's HelloRequest message, the server will immediately send a new session ID that the client will honor. Without the 'once' setting, the session ID will disappear across TCP sessions.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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