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

XNAT service admin accounts need to be accessible in the admin UI

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.2
    • Component/s: Admin UI
    • Labels:
      None
    • Sprint:
      1.7.1 Release Sprint 1
    • Rank:
      0|ii127z:
    • Sprint:
      1.7.1 Release Sprint 1

      Description

      The "receivedFileUser" for autoarchiving sessions and "primaryAdminUsername" for building session XML need to be accessible in the admin UI. Also, the requirement to restart tomcat should go away.

        Issue Links

          Activity

          Hide
          jrherrick@wustl.edu Rick Herrick added a comment -

          Improved handling of updated provider preference settings in the handler method. Removed redundant setReceivedFileUser() method from API implementation.

          Changes in UI should take effect as preferences as soon as they're saved. Any subsequent operations that reference the user provider should use the updated user object.

          Show
          jrherrick@wustl.edu Rick Herrick added a comment - Improved handling of updated provider preference settings in the handler method. Removed redundant setReceivedFileUser() method from API implementation. Changes in UI should take effect as preferences as soon as they're saved. Any subsequent operations that reference the user provider should use the updated user object.
          Hide
          moore.c@wustl.edu Charlie Moore added a comment -

          I had to restart tomcat to get the changes to take effect (AutoRun failed because the alias token it had was for the disabled 'admin' account). Side note: it looks like that used the Primary Admin Account, and not the Received File User like I thought.

          Show
          moore.c@wustl.edu Charlie Moore added a comment - I had to restart tomcat to get the changes to take effect (AutoRun failed because the alias token it had was for the disabled 'admin' account). Side note: it looks like that used the Primary Admin Account, and not the Received File User like I thought.

            People

            • Assignee:
              moore.c@wustl.edu Charlie Moore
              Reporter:
              moore.c@wustl.edu Charlie Moore
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours
                2h

                  Agile