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

Enhance AgendaAuthorizationServiceImpl so that more than one permission can exist for agenda maintenance

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-b3, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7536getPermissionTypeServicesByTemplateId can fetch permission type more than once
      KULRICE-8857Permission doc says the max length of the Permission Name is 40 characters but KFS has existing values that exceed that
      KULRICE-1529enhance multiLineLookup to support edit
      KULRICE-2731Allow for BusinessObjectService to persist to more than one data source
      KULRICE-5185New version of rice is not supporting maintaining collection with more than one level depth.
      KULRICE-2853Test that the BusinessObjectService can persist/query to more than one datasource
      KULRICE-8844KualiDocumentFormBase permission checks are more expensive than they have to be
      KULRICE-3290Factor out incident report code so that it can be used from more than just a Struts context
      KULRICE-14024If you do more than one context search in an agenda document you get an STE
      KULRICE-8579Predicate does not work correcty if there is more than one attribute for KRIM_RSP_ATTR_DATA_T added to it
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently, the PermissionService.isAuthorized(...) call made inside AgendaAuthorizationServiceImpl.isAuthorized(...) has a hard coded namespace, and the AgendaEditorAuthorizer uses a hard coded permission name. That combination seems to make it so that there can only be 1 permission for agenda editing. Seems like this should be enhanced so that client apps can add permissions for agenda maintenance under their own namespaces.

        Issue Links

          Activity

          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #267 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/267/)
          KULRICE-5996 Display error after Context lookup if the user is not authorized for it.
          KULRICE-5996 Database scripts
          KULRICE-5996 Use namespace of context for permission's name space. Since a new agenda does not have a context until routing, any user can add an agenda. However, the contexts' namespace is checked for permission on routing.

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #267 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/267/ ) KULRICE-5996 Display error after Context lookup if the user is not authorized for it. KULRICE-5996 Database scripts KULRICE-5996 Use namespace of context for permission's name space. Since a new agenda does not have a context until routing, any user can add an agenda. However, the contexts' namespace is checked for permission on routing.
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              Claus Niesen
              Reporter:
              Peter Giles (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel