[KULRICE-4641] Fix Remote Mode in KIM Created: 05/Oct/10  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Version Compatibility
Affects Version/s: None
Fix Version/s: Backlog

Type: Task Priority: Major
Reporter: Matt Sargent Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: 3 weeks
Time Spent: Not Specified
Original Estimate: 3 weeks

Issue Links:
relates to KULRICE-4140 KimTypeInfoService cannot be accessed... Closed
Similar issues:
KULRICE-9221Invalid bean name "matchAllTxInterceptor" for KIM Remote mode
KULRICE-2721Add switch on KIM Configurer to make run in local or remote modes
KULRICE-4666Evaluate "remote" KIM services
KULRICE-4303Document initiator check fails when KIM is run in remote mode
KULRICE-4668Evaluate remote KIM services: implementation
KULRICE-4667Evaluate remote KIM services: analysis & decision
KULRICE-3721The "remote" run mode for KIM (and other Rice modules?) does not allow proper consumption of services from the bus
KULRICE-4140KimTypeInfoService cannot be accessed by "remote" KIM clients directly
KULRICE-6683Add a "THIN" client run mode to KEW, KIM, and KSB modules
KULRICE-7354Standalone server is attempting to load remotable attributes locally
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


fix "remote" mode in KIM, currently broken in KNS, transactional issue
1. do analysis to determine "how" to fix it, possibilities include
1. modifying KNS so that it doesn't do these kinds of derived roles
2. modifying the KIM apis so that they can pass additional context along that can be used for role derivation purposes

Generated at Wed Jun 03 04:36:40 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.