Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-8490

Recall Routing permissions do not work with KC role qualifiers

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      KIM Integration
    • Application Requirement:
      KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      In trying to complete KRACOEUS-4686 we discovered that some Rice services do not work with KC's role qualifiers. Specifically in DocumentTypePermissionServiceImpl, which is called when trying to record any action taken, buildDocumentIdRoleDocumentTypeDocumentStatusQualifiers provides role qualifiers that will never match KC's necessary role qualifiers.

      Most of KC's roles required the unit number or the primary key of the BO(proposal number, protocol id, etc). DocumentTypePermissionsSerivceImpl primarily provides document number for this type of role qualification which KC does not use. This is a problem with the recall action as there is no way to work around the permission check as with other actions(canSave, canRoute, etc).

      We therefore need a way to workaround the permission check in canRecall in DocumentTypePermissionServiceImpl as seen in canSave(parameter) or in canRoute(document policy). Or, and we think more preferred long term, we need a way to inject application specific role qualifiers into this service so permissions checks can work as designed.

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                cniesen Claus Niesen
                Reporter:
                gathreya Gayathri Athreya
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: