[DOCU-3436] Proposed YAML configuration for sticky session leads to errors Created: 05/Feb/24  Updated: 05/Feb/24  Resolved: 05/Feb/24

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Michael Evelt Assignee: Alex Mansell
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Documentation page URL: https://docs.magnolia-cms.com/paas/configuration/sticky-sessions.html
Reporter Name: Michael Evelt
Email: m.evelt@lvm.de

 Description   

We tried to use the additonal ingress configurations as defined in the referenced documentation page.
There are two issues with this:
1) nginx.ingress.kubernetes.io/session-cookie-max-age: 10

The number of seconds needs to be set as a string, otherwise (at least on our system) the yaml cannot be parsed properly. This configuration works perfectly fine:
nginx.ingress.kubernetes.io/session-cookie-max-age: "10"

 

2) The proposed alternative for the cookie-name JSESSIONID does not work in combination with the SSO module (not sure it it works for non SSO authentication). To clarifiy:

This configuration works

nginx.ingress.kubernetes.io/session-cookie-name: "INGRESSCOOKIE"

This configuration leads to the tomcats 403 page:

nginx.ingress.kubernetes.io/session-cookie-name: "JSESSIONID"

 

Best wishes!



 Comments   
Comment by Michael Evelt [ 05/Feb/24 ]

Great, thank you!

Generated at Mon Feb 12 01:36:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.