Uploaded image for project: 'Kuali Rice Roadmap'
  1. Kuali Rice Roadmap
  2. KRRM-22

Implement "update" operations for the various KIM services

    Details

    • Type: Rice Enhancement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: KR 2.0
    • Component/s: KIM
    • Labels:
      None
    • Rice Theme:
      Service Orientation
    • Priority Score:
      10
    • Functional Justification :
      Hide
      The main functional impact here would lie upstream of the KIM services. In certain cases, a client application may want to update KIM data that it does not have access to currently via the existing update service operations. The was fairly important for changing of role and group membership which is why those apis were added in the original KIM implementation.

      This would additionally allow for the functional user interface screens in KIM to be built on top of these service operations which would ease implementation and customization of institutions.
      Show
      The main functional impact here would lie upstream of the KIM services. In certain cases, a client application may want to update KIM data that it does not have access to currently via the existing update service operations. The was fairly important for changing of role and group membership which is why those apis were added in the original KIM implementation. This would additionally allow for the functional user interface screens in KIM to be built on top of these service operations which would ease implementation and customization of institutions.
    • Technical Justification:
      Hide
      In an enterprise infrastructure, some of the update operations which are missing currently could be useful. For example, when scripting changes which might affect role qualifiers or permission details, the ability to update this information via an API would come in handy.
      Show
      In an enterprise infrastructure, some of the update operations which are missing currently could be useful. For example, when scripting changes which might affect role qualifiers or permission details, the ability to update this information via an API would come in handy.
    • Priority - KFS:
      Medium
    • Priority - KC:
      Medium
    • Priority - KS:
      High
    • Priority - Rice:
      High
    • Theme:
      Service Orientation, Kuali Application Business Drivers
    • Application Impact:
      Low
    • Effort Estimate:
      Low ~ 200 hrs

      Description

      We have some of these but they are by no means comprehensive.

      Summary of Work Involved: From below "The main functional impact here would lie upstream of the KIM services. In certain cases, a client application may want to update KIM data that it does not have access to currently via the existing update service operations. The was fairly important for changing of role and group membership which is why those apis were added in the original KIM implementation. This would additionally allow for the functional user interface screens in KIM to be built on top of these service operations which would ease implementation and customization of institutions." There would be work to identify what additional methods we actually need to KIM, however a starting framework for starting on this is in the JIRA.

        Attachments

          Issue Links

            Activity

            Hide
            cfairlie Cath Fairlie (Inactive) added a comment -

            KS comment - We would like to see these implemented as remotable service calls (web service).

            Show
            cfairlie Cath Fairlie (Inactive) added a comment - KS comment - We would like to see these implemented as remotable service calls (web service).
            Hide
            ewestfal Eric Westfall added a comment -

            I can champion this item unless someone from KS wants to.

            Show
            ewestfal Eric Westfall added a comment - I can champion this item unless someone from KS wants to.
            Hide
            lschultz Lori Schultz (Inactive) added a comment -

            Additional information would be helpful to properly analyze this for ranking.

            Show
            lschultz Lori Schultz (Inactive) added a comment - Additional information would be helpful to properly analyze this for ranking.
            Hide
            ewestfal Eric Westfall added a comment -

            As far as scope for this item, it think it would include an analysis of the following service to determine what additional api methods should be added to support operations to update various pieces of KIM data:

            1) IdentityService
            2) GroupService
            3) RoleService
            4) PermissionService
            5) ResponsibilityService

            One important thing to consider here is that in most of these cases I suspect that we may want certain update operations to be optional (especially in terms of the IdentityService since it may often be the case where it backed by a directory service which the application shouldn't have the ability to update)

            Show
            ewestfal Eric Westfall added a comment - As far as scope for this item, it think it would include an analysis of the following service to determine what additional api methods should be added to support operations to update various pieces of KIM data: 1) IdentityService 2) GroupService 3) RoleService 4) PermissionService 5) ResponsibilityService One important thing to consider here is that in most of these cases I suspect that we may want certain update operations to be optional (especially in terms of the IdentityService since it may often be the case where it backed by a directory service which the application shouldn't have the ability to update)
            Hide
            sagee Sandra Agee (Inactive) added a comment -

            This scope is confirmed

            Show
            sagee Sandra Agee (Inactive) added a comment - This scope is confirmed
            Hide
            ewestfal Eric Westfall added a comment -

            This was actually done as part of 2.0 during the web service and version compatibility work. So I'm going to close this issue and am tagging the fix version as KR 2.0.

            Show
            ewestfal Eric Westfall added a comment - This was actually done as part of 2.0 during the web service and version compatibility work. So I'm going to close this issue and am tagging the fix version as KR 2.0.

              People

              • Assignee:
                ewestfal Eric Westfall
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: