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

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 Sun Jan 24 05:33:32 CST 2021 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.