Details
-
Type:
Sub Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: 2.0
-
Component/s: Analysis, Version Compatibility
-
Labels:None
-
Similar issues:
KULRICE-4666Evaluate "remote" KIM services KULRICE-4668Evaluate remote KIM services: implementation KULRICE-4641 Fix Remote Mode in KIM KULRICE-3455Possible issues with remoting of KIM Type Services and attributes KULRICE-3721The "remote" run mode for KIM (and other Rice modules?) does not allow proper consumption of services from the bus KULRICE-4366cannot connect to remote kfs services KULRICE-4140KimTypeInfoService cannot be accessed by "remote" KIM clients directly KULRICE-5069Determine best strategy for declaring/throwing exceptions from (remote) service layer KULRICE-5224Convert RuleValidationAttribute to a remotable SOAP service KULRICE-5229Convert KIM role, permission, and responsibility "type" services in KEW to their SOAP remoted form -
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
1. Figure out if remote kim is possible.
2. set up a kim client, an application that uses kim in remote mode (we currently have some unit tests)
3. define some custom permissiontypeServices and custom roleTypeServices.
4. It might be best to use KFS for this... because they already define both the permissionTypeService and the roleTypeServices.
5. Integrate KFS with standalone rice. Custom servlet that has calls into the IDM service to do authorization checks. Need to make sure it's checking permissions and roles in kim that the rice standalone server will need to call back into the client for. .. ie. Chart/Org. This will test the "round trip" for us. We would want to test the speed of identity and group service operations. Switch kfs to run in embedded kim mode and run the same set of tests to compare the speed results. That will give us an idea of how kim performs in remote vs embedded mode.
