Evaluate "remote" KIM services (KULRICE-4666)

[KULRICE-4668] Evaluate remote KIM services: implementation Created: 06/Oct/10  Updated: 06/Jun/14  Resolved: 29/Jun/11

Status: Closed
Project: Kuali Rice Development
Component/s: Development, 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: 12 weeks
Time Spent: Not Specified
Original Estimate: 12 weeks

Similar issues:
KULRICE-4666Evaluate "remote" KIM services
KULRICE-4667Evaluate remote KIM services: analysis & decision
KULRICE-5319Implement caching on remote soap services
KULRICE-4140KimTypeInfoService cannot be accessed by "remote" KIM clients directly
KULRICE-6511Implement ability to load remote services lazily
KULRICE-5632Implement KewModuleService so that document and document type ebos are loaded through remote services
KULRICE-3455Possible issues with remoting of KIM Type Services and attributes
KULRICE-4917Load test development & implementation
KULRICE-2315Implement caching of data to the IdentityManagementService implementation
KULRICE-3721The "remote" run mode for KIM (and other Rice modules?) does not allow proper consumption of services from the bus
KAI Review Status: Not Required
KTI Review Status: Not Required

 Description   

This depends on the results of the analysis task - if they're close enough in speed we need to start tweaking

1. Just embedding the authorization system.
2. but still doing remote identity, group, and role.
3. look at adding additional caching on either the client or server side
4. if we did move forward with kim in remote mode we would need to find out transactional operation... updating groups / roles. We would use messaging for this... instead of synchronous updates. That's because if you use messaging the message wont be sent until the transaction completes. Downside, is that the update will be asynchronous... Figure this out.



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

Closing since these items are now in the release notes.

Generated at Sat Jun 06 21:13:24 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.