Task #2105
closed
Dynamic form for identities
Added by Radek Tomiška about 4 years ago.
Updated about 4 years ago.
Description
Feature will cover requirement to configure different form to create and edit different type of identity (externist vs. internist):
- new field with type (~codelist) will be added to identity - will control, which form will be used
- identity type can be switched - new identity permission will be added
- new type can be registered (~by codelist item)
- when new identity is created, then modal window with available identity types will be shown. If only one type is available => then form will be shown imediatelly (=> default / current form will be shown).
Files
- Related to Task #2153: Autorization policies - add evaluator by user type (projection) added
- Related to Task #2154: Automatic roles: Support user type field (projection) in automatic role by attribute added
- Related to Task #2155: Support user type field (projection) in synchronization and provisioning added
- % Done changed from 0 to 80
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 80 to 90
- Related to Task #2162: Bulk action - change user type (projection) added
- Related to Task #2163: Authorization policies - support secured contract eav attributes by default added
- Related to Task #2164: Authorization policies - support secured identity eav attributes by default added
- Related to Task #2165: Authorization policies - check change user type permission on backend added
Fixed review notes:
- authorities was evaluated only on form projection => permissions were ignored
- user type is removed from basic fields available for form projection
- username is required for updata by projection (the same behavior as defaul form)
- doc improved, update identity permission is needed to submit projection form (can be improved in future)
Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/e8b7d45802711ceb48a093a9b8bbf840eaa6f632
I did review and test. This is very big and complex feature. Works nice and code looks also nice. Nice tutorial! Thanks for this.
I tested again the issues we consulted and what you fixed. Everything works well now, expect one thing:
If my user can updated his identity full detail (firstname...), then projection detail can be saved, but identity fields are read-only.
Notes:
- Role with attributes are not fully supported for create new identity now. Maybe warning in the wiki should be created for it.
- You changed version of the selectbox from 1.3 to 1.2. I was a intent?
- Wiki: Should be not IdmFormDefiniton: Permission to autocomplete form projections: Forms - projections(IdmFormDefiniton) | View in select box (autocomplete) | BasePermissionEvaluator
- Related to Defect #2190: Read only on form doesn't work properly - AbstractFrom added
My issues with wrong read only form, is related to AbstractForm and will be solved within #2190. I have removed the readOnly property "workaround". The form now works correctly.
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Thx for help! I retest permissions again and workaround works.
- Status changed from Resolved to Closed
- Related to Defect #2567: Automatic role by EAV is not assigned when setting the EAV together with entity (e.g. through form projection) added
Also available in: Atom
PDF
