Evaluate "remote" KIM services (KULRICE-4666)

[KULRICE-4667] Evaluate remote KIM services: analysis & decision Created: 06/Oct/10  Updated: 06/Jun/14  Resolved: 29/Jun/11

Status: Closed
Project: Kuali Rice Development
Component/s: Analysis, Version Compatibility
Affects Version/s: None
Fix Version/s: 2.0

Type: Sub Task Priority: Major
Reporter: Matt Sargent Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: 2 weeks
Time Spent: Not Specified
Original Estimate: 2 weeks

KAI Review Status: Not Required
KTI Review Status: Not Required


1. Figure out if remote kim is possible.
2. set up a kim client, an application that uses kim in remote mode (we currently have some unit tests)
3. define some custom permissiontypeServices and custom roleTypeServices.
4. It might be best to use KFS for this... because they already define both the permissionTypeService and the roleTypeServices.
5. Integrate KFS with standalone rice. Custom servlet that has calls into the IDM service to do authorization checks. Need to make sure it's checking permissions and roles in kim that the rice standalone server will need to call back into the client for. .. ie. Chart/Org. This will test the "round trip" for us. We would want to test the speed of identity and group service operations. Switch kfs to run in embedded kim mode and run the same set of tests to compare the speed results. That will give us an idea of how kim performs in remote vs embedded mode.

Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]

Closing since these items are now in the release notes.

Generated at Sat Apr 17 04:05:33 CDT 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.