Forum Discussion
Cookie persistence and source address fallback
- Apr 20, 2015
You are correct when putting Cookie and Source Persist together. If there is a persist record it will go to that server and cluster all the clients that share the same IP to the same server.
You have added two different persistence profiles to the virtual server, "Keycloak_cookies" and "keycloak_pers_sourceaddr". Since "Keycloak_cookies" is set as the default persistence profile (default yes), then this will always be used. "keycloak_pers_sourceaddr" which is set to "default no" will never be used unless you call it using an iRule. Is this the behaviour that you wanted?
If not, then your intention may have instead been to have cookie persistence as the primary persistence method and source IP persistence as the fallback persistence. This would be configured like so:
tmsh modify ltm virtual vs_https persist replace-all-with { Keycloak_cookies { default yes } } fallback-persistence keycloak_pers_sourceaddr
and this is ok? It looks like only persistance profile is used and fallback not exists:
persist {
Keycloak_cookies {
default yes
}
}
- Feb 26, 2025
The output you shared shows that only cookie persistence will be used. You are correct, fallback persistence is not configured.
- kbksFeb 26, 2025
Altostratus
I used Your command You provided. And the result of "tmsh show running-config ltm virtual vs_https" shows that.
- Feb 26, 2025
In the command output there should be a line before the "persist" configuration that you previously showed which states "fallback-persistence keycloak_pers_sourceaddr".
Could you confirm that it's there?
Recent Discussions
Related Content
* 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