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

Reorder calling of authorizers and presentation controllers


    • Type: Task Task
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-8049Remaining Authorization and Presentation Controller Work
      KULRICE-5339Finish integration with presentation controller/authorizer/AttributeSecurity checking KIM
      KULRICE-5371Uif Framework - Collections: Hook in authorization
      KULRICE-8565Collection table starts not displaying after returning from a controller called dialog.
      KULRICE-11388Create Automated Functional Tests for KRAD Labs - Maintenance Sample - Presentation Controller
      KULRICE-8353Lookup controller does not check return of validation call
      KULRICE-13730Create Web Tests for KRAD Maintenance Document View Presentation Controller
      KULRICE-11321Create Automated Functional Tests for KRAD Labs - Inquiry - Presentation Controller hiding field and section
      KULRICE-11882AFT Failure lookup results no longer present
      KULRICE-7184Please provide a framework or api call to allow access to CacheManagers
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:


      In ApplyAuthAndPresentationLogicTask many of the permissions checks call the authorizer before the presentation controller. This order is not consistent with either other parts of the system or the KNS. We should be checking the presentation controller before the authorizer. This would help things like pessimistic locking know that when they do their checks in the authorizer that the field or group that they are checking will not be set as read only after they do their checks. It also makes sense from a predictable ordering standpoint.

      We should probably also rename the class as well.


        There are no comments yet on this issue.


          • Assignee:
            Kristina Taylor (Inactive)
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Structure Helper Panel