Task #170
closed
Provisioning - add agends for system-attribute mapping/handling
Added by Vít Švanda about 8 years ago.
Updated about 8 years ago.
Category:
Identity connectors
Description
In erdiagram (in master) was added new classes for mapping and handling system's attributes.
We will need implement new agendas:
- System schema definitions
- System entity handling (with system attribute handling).
Connectors are develop in "Connectors" branche for now.
- Status changed from New to In Progress
- Assignee changed from Radek Tomiška to Vít Švanda
I added new entity for SchemaAttribute, SchemaAttributeHandling, SchemaObjecClass, SystemEntityHandling
I added new tab for Schema on system and created list of schema attributes with detail.
- Added tab to system, contains list of groups (mapped attributes on entity and operation type).
- Added subagenda for create mapping IDM attribute to schema attribute.
Added method for generate schema for connector
- Description updated (diff)
- Status changed from In Progress to Needs feedback
- Assignee changed from Vít Švanda to Radek Tomiška
- % Done changed from 0 to 90
- Status changed from Needs feedback to In Progress
- Assignee changed from Radek Tomiška to Vít Švanda
I did test and code review:
- code looks nice (FE and BE)
- DefaultSysSystemEntityHandlingService. findBySystem could return one record? Or specific method without paginable on repository could be created.
- after schema attribute is saved, then redirect to schema class detail (back) should be done
- schema attribute data type could be enumeration maybe .. we could make SystemService.supportedConnectorPropertyMapping public and use them on all sides (in new ticket)? Makes it sense?
- i've hidden unimplemented options from enumeration (group, synchronization ...) - only identity provisioning is supported now
- we need referential integrity #226 to be done necessarily - error occurs, when some attribute from schema is removed, and is used in mapping etc. (will be solved in #226)
- component ScriptArea looks very nice
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
- after schema attribute is saved, then redirect to schema class detail (back) should be done Implemented
schema attribute data type could be enumeration maybe .. we could make SystemService.supportedConnectorPropertyMapping public and use them on all sides (in new ticket)? Makes it sense?
-- Object type for schema is return by connector ... I thing static definition is not good idea
- Status changed from Resolved to Closed
Also available in: Atom
PDF
