Defect #2980
closed
Can't edit already assigned role with unique role attribute
Added by Alena Peterová over 2 years ago.
Updated over 2 years ago.
Description
Tested on 11.1.1. Previous versions had similar issue #2842.
The role has a required unique attribute.
We change the validity of the assigned role (we don't change anything else):
The role request fails with the following exception:
2021-10-14T13:14:08.407474+02:00[Europe/Prague]: Identity-role [7a7448d5-5be4-4981-a11d-ee7d478ceed0] (for role [PRISTUP]) has unvalid attribute [idCardNumber]!
Files
- Assignee changed from Radek Tomiška to Vít Švanda
- Status changed from New to In Progress
- % Done changed from 0 to 40
- Target version set to 12.0.0
- % Done changed from 40 to 90
Fixed. The problem was in a situation where the request was performing a validation of the uniqueness of the value at the identity-role and at the same time against the same value in the request concept. The fact that the uniqueness validation is done in both "stacks" is useful at the time of creating a new concept (here we need to know that the value is already used at some identity-role). For this reason, I created a new parameter (validateOnlySameOwnerType) in the attributes validation that allows to enable the check only for the same entity type.
Commit: https://github.com/bcvsolutions/CzechIdMng/commit/245a5d758eb2f59355f0f12142592babaeecc73e
- Related to Defect #2842: Audit displays misleading warning for a unique role attribute, can't edit already assigned role added
- Status changed from In Progress to Needs feedback
- Assignee changed from Vít Švanda to Radek Tomiška
- Target version changed from 12.0.0 to 11.2.2
- Status changed from Needs feedback to Closed
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 90 to 100
I did test and code rewiew, it works, thx!
Also available in: Atom
PDF
