Type: Sub Task
Affects Version/s: None
Fix Version/s: 2.0
KULRICE-4666 Evaluate "remote" KIM services KULRICE-4667 Evaluate remote KIM services: analysis & decision KULRICE-5319 Implement caching on remote soap services KULRICE-4140 KimTypeInfoService cannot be accessed by "remote" KIM clients directly KULRICE-6511 Implement ability to load remote services lazily KULRICE-5632 Implement KewModuleService so that document and document type ebos are loaded through remote services KULRICE-3455 Possible issues with remoting of KIM Type Services and attributes KULRICE-4917 Load test development & implementation KULRICE-2315 Implement caching of data to the IdentityManagementService implementation KULRICE-3721 The "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
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.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Duplicate [ 3 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||custom [ 87149 ]||Copy of custom for rice [ 212296 ]|
|Workflow||Copy of custom for rice [ 212296 ]||custom [ 222044 ]|
|Workflow||custom [ 222044 ]||Rice Workflow [ 231792 ]|
|Reporter||Jessica Coltrin [ jcoltrin ]||Matt Sargent [ masargen ]|