Uploaded image for project: 'Runtime'
  1. Runtime
  2. RUNTIME-2620

The iteration over access controllers is stopped as soon as a controller throw a error

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 4.0.4, 4.1.0
    • None
    • None
    • None
    • 4.1 M5

      Calling #getAllowedUsers, #hasRight, #getReadAccessAllowedUsers, ....

      If during iteration on access controllers, an access controller failed, the iteration is stopped and there is no error in logs.

      My use case:

      • while checking reader rights on archived contents, ThesaurusAccessController throws an error in #isSupported method
      • there is no error in logs
      • then no others controllers have been called
      • so there is no result found in search archives

      If a controller throws a error, it should be catched, logged, consider as "UNKNOWN" result, and continue to iterate over controllers

            sprieul Simon Prieul (Inactive)
            laurence Laurence Aumeunier
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: