Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCU-3436

Proposed YAML configuration for sticky session leads to errors

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Neutral
    • None
    • None
    • None
    • None

    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!

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              amansell Alex Mansell
              mevelt Michael Evelt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: