Actions
Feature #2550
closedExport+import of a virtual system - empty additional attributes in virtual requests, error when using the "rights" attribute
Start date:
11/02/2020
Due date:
% Done:
100%
Estimated time:
24.00 h
Owner:
Description
Tested on the version 10.4.7
Export + import of a virtual system doesn't create the virtual system with the same attributes (in VsAccount form definition), which leads to some issues when using this imported system.
A) "rights" attribute causes errors when implementing the virtual requests- Create a virtual system
- Export the system
- Import the system
- Create 2 roles which assign the system and set some value to the "rights" attribute
- Assign the roles to a user
- Mark the virtual request as implemented - not possible, red message "Some error occured on server" appears
2020-11-02 19:01:58.887 ERROR 4184054 --- [http-nio-8080-exec-2] e.b.i.c.e.ExceptionControllerAdvice.handle : [65338c09-0303-4028-8124-0e5b7883a858] java.lang.IllegalArgumentException: Form attribute [czechidm:virtual-system-basic:eu.bcvsolutions.idm.vs.connector.basic.BasicVirtualConnector:1.0.1:systemId=e88a55cf-f62d-4cb6-92e1-29e904873d19:rights] does not support multivalue, sent [2] values. at eu.bcvsolutions.idm.core.eav.service.impl.DefaultFormService.saveAttributeValues(DefaultFormService.java:592) at eu.bcvsolutions.idm.core.eav.service.impl.DefaultFormService.saveValues(DefaultFormService.java:543)
Note: Maybe connected to this #2398?
B) additional empty attributes in virtual requests- Create a virtual system (without default role in my case)
- Remove some of the attributes - phone, titleBefore, titleAfter, rights (https://wiki.czechidm.com/tutorial/adm/virtual_system_-_adding_or_deleting_managed_extended_attributes#deleting_attributes_on_virtual_systems)
- Export the system
- Import it to some other instance of IdM
- Create a role for the system
- Add the role to some user
- Mark the virtual request as implemented
- Change the last name of the user
- The virtual request contains empty attributes that shouldn't be there (which is confusing, especially when there is a lot of them)
Workaround: Delete the additional attributes from the VsAccount form definition of the imported system
Attached is the exported ZIP file and the screenshots of the form definition "VsAccount" from both instances. We can see the additional attributes in the imported instance that shouldn't be there.
Note: If we add some new singlevalued attributes different from the default attributes, they are imported correctly
Files
Related issues
Actions