Uploaded image for project: 'XNAT'
  1. XNAT
  2. XNAT-6889

Project access changes don't propagate across nodes

    XMLWordPrintable

Details

    • Bug
    • Status: Reopened
    • Critical
    • Resolution: Unresolved
    • 1.8.3
    • 1.8.5
    • Multinode
    • XNAT 2021-Q4 Sprint 2
    • Rank:
      0|0hzycd:zzzr07zzzzxzzz
    • XNAT 2021-Q4 Sprint 2

    Description

      When a user is granted access to a project in a multinode-XNAT environment, they often won't be able to access the new project. The reason for that is that the user is (in general) accessing XNAT via a node other than the one on which another user granted them access, and the cache on the user's node hasn't been updated. It can be worked around by using the "Reset Access Cache" button on the user self-management page (from clicking the link on the user's username in the top right of the page), but that's suboptimal.

      Attachments

        Activity

          People

            jrherrick@wustl.edu Rick Herrick
            moore.c@wustl.edu Charlie Moore
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: