Defect #2037
closed
In the attribute mapping configuration I can select any existing mapping
100%
Description
Affected version: 10.0.0
Open a detail of a system, go to Mapping tab, open a mapping configuration (synchronization or provisioning - it doesn't matter) and open any attribute detail. Now if you click on the "Mapping name" field you can select any existing mapping from any system that exists in IDM from the drop down menu and save. The attribute will appear in the selected mapping after that but mapped on the schema attribute from the previous system. I can even delete the mapping name but the validation won't let you save.
In 9.x versions the field "Mapping name" was disabled or there couldn't be set a mapping from another system.
Related issues
Updated by Radek Tomiška about 4 years ago
- Related to Defect #1927: Wrong behavior of a frontend component in the section of system mapping. added
Updated by Vít Švanda about 4 years ago
- Assignee changed from Vít Švanda to Ondrej Husník
Updated by Ondrej Husník about 4 years ago
- Status changed from New to Needs feedback
- Assignee changed from Ondrej Husník to Vít Švanda
- Target version set to 10.1.0
- % Done changed from 0 to 90
The behavior of mapping name item was changed by mistake from readOnly state to editable one during changes in #1927. It should be always disabled.
Please check my fix. Thanks in advance.
https://github.com/bcvsolutions/CzechIdMng/pull/80/commits/963ee90303f05f01ac32c81acc188aed226ea782
Updated by Vít Švanda about 4 years ago
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Ondrej Husník
- Priority changed from Normal to Low
- % Done changed from 90 to 100
I did review and test, work correctly now. THX
Updated by Radek Tomiška about 4 years ago
- Status changed from Resolved to Closed