Details
-
Type:
Task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Backlog
-
Component/s: Version Compatibility
-
Labels:
-
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-4303 Document 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:KIM
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
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
Issue Links
- relates to
-
KULRICE-4140
KimTypeInfoService cannot be accessed by "remote" KIM clients directly
-
- Trackbacks
-
![[Confluence: Cynergy]](/images/icons/generic_link_16.png "[Confluence: Cynergy]")
Cynergy 2.1 Upgrade Highlights and Concerns
Still under construction Common Changes Dependency Changes for Rice 1.0.2 and Rice 1.0.3 A significant number of dependencies were added, updated, and removed for the Rice 1.0.3 release, where the complete list is available by going to the 1.0....
