Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-6851

Struts configuration problem with Authorization Exception Handler

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-rc4
    • Fix Version/s: 2.0.1
    • Component/s: Configuration
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-4542Create Authorization Exception Handler for graceful handling of DocumentAuthorizationException
      KULRICE-4543Exception and incident handling framework improvements
      KULRICE-7557Large attachments on notes and attachments framework cause exceptions
      KULRICE-2177Consolidate all Rice Struts modules into a single struts module
      KULRICE-2662Hook up Routing Rule and Routing Rule Delegation maintenance document handlers
      KULRICE-1517Strange transaction demarcation when invoking exception handler from KSB
      KULRICE-852Workgroup xml handler allows workgroups with duplicate members
      KULRICE-3879Problems with Rice metadata
      KULRICE-3886PDF documents with ampersand in the content cause exception
      KULRICE-501Rice Template struts-config.xml missing PojoPlugin.xml causing JSP rendering problems
    • Rice Module:
      Rice Core
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I tried to test with the struts-config.xml in ksb/WEB-INF and found that the rice team had made some changes the global-forward path for exceptionIncidentHandler, but not for authorizationExceptionHandler.

      <forward name="exceptionIncidentHandler" path="/../kr/kualiExceptionIncidentReport.do" />
      <forward name="authorizationExceptionHandler" path="/kr/authorizationExceptionReport.do" />

      Changing the forward path of authorizationExceptionHandler to path=" /../kr/authorizationExceptionReport.do" seems to fix the problem

      There is a work around. Just login as the correct user and avoid the authorization error

        Issue Links

          Activity

          Hide
          Dan Lemus (Inactive) added a comment -

          KFSMI-7367 may be related to this as well. It throws a stack trace when an invalid user is backdoored in. It could be because the authorization handler isn't picking it up and giving a nice message that the user is not authorized (or is invalid).

          Show
          Dan Lemus (Inactive) added a comment - KFSMI-7367 may be related to this as well. It throws a stack trace when an invalid user is backdoored in. It could be because the authorization handler isn't picking it up and giving a nice message that the user is not authorized (or is invalid).

            People

            • Assignee:
              Jeremy Hanson
              Reporter:
              Dan Lemus (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel