Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-17688

InMemoryCtsSessionCacheStep#cacheTrusted field should be marked volatile

    XMLWordPrintable

    Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.0.0.6, 7.0.1
    • 6.5.4, 7.0.2, 2021.5, 7.2.0
    • session
    • AM Sustaining Sprint 84, AM Sustaining Sprint 85
    • 2

      Description

      Bug description

      The InMemoryCtsSessionCacheStep#cacheTrusted field is being accessed by one thread and changed potentially by another. This field has not been marked as volatile, and hence it is possible that changes made to the field in one thread may not be picked up immediately by other threads.
      This in essence can potentially mean that the cache may be considered trusted when it isn't, or the cache may be considered untrusted even after it became trusted again.

      How to reproduce the issue

      Don't have specific steps, this was found through code analysis.

      Expected behaviour

      cacheTrusted field should be protected for multi-thread access.

      Current behaviour

      It isn't.

        Attachments

          Activity

            People

            joe.starling Joe Starling
            peter.major.fr Peter Major
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: