IdStory Identity Manager

Added new framework (czechidm) to IC module.
- Implemented load of connector info.
- Implemented load of default connector configuration. (Configuration is now "hard" coded in connector implementation ... TODO)

• Load default connector configuration from configuration-class (for czechidm framework) implemented.
• Created basic configuration for VS

• Propagate system ID to VS connector (through czechidm connector framework).
• Created create, update, delete, read operations (interfacase).
• Implemented operations to Czechidm framework (call connector).

• Create, Update, Read operation on VS connector implemented

Create entity, repository, service, controller for VsRequest and VsRequestBatch.

• Created backend for VsRequestImplementer.
• Interface and methods for internal call CUD (realization) operations on VS connector.
• Started with implementing start and execute VsRequest.
• Added support for event on VsRequest.

• Finding duplicities
• Finding previous request and create relations.

• Merged VS BE module to develop.
• Create first version of VS frontend module.

• Operations for realize and cancel request is implemented on FE (request detail)
• System DTO is now added to embedded map.

• Acc module - refactored method (and api) for read object from connector
• Added REST method for load object form connector (by virtual system request)
• Show attributes form connector on VS request detail.

• Highlight changes between VS request attributes and VS account attributes - Part 1

• Solving problem with cycling during render table with notrivial data (span, div...).

• Problem occures when is some changed attribute returned to previous value.
• This situation is by provisioning evalued as none change and none VS request is created.
• I had to rewrite basic evaluation of changes.

• Connector read method now return not 'real' vs account persist in VsAccount, but merge they with changes from all unresolved requests for same UID.
• This behavior is implemented for all operations Create, Update, Delete.

Was implemented operation for cancel all requests created before 'deleting' request.

• Do update when VS account already exist - implemented.

• Added table (entity, service, flyscript) for VsSystemImplementer.
• This table keeps relation on identity or on role.
• Implemented update VsSystemImplementer by VS configuration.
• Roles are now joined to implementers (his identities)

• Cancel operation now use progressbar.
• If is not set none implementer's role (in connector configuration), then is use default role.

Added security for VsRequests ... by implementers ... role remaining.

• Created ENG localization for FE.
• VS module added to aggregator.
• Updated ERDiagram for VS entities.

• Notification detail - Added tab with plain html and rendered html message.
• Fixed problem with audit fields on VsRequest
• VS now supported enable/disable operation

Created seven tests for VsRequestService.

• I created next tests. Now we have fourteen tests, this tests coveraging 82% of code in VS module.
• Default role with implementers are now used only if none roles and direct impelementers are set.

Ready for test:

Created tutorial for create virtual system in wiki https://wiki.czechidm.com/tutorial/dev/how_to_create_virtual_system
Created documentation in wiki: https://wiki.czechidm.com/devel/dev/virtual-systems#virtual_connector
All is in develop branche.
Tests are in VS module.

Rostislav Novotný wrote:

After the creation of the new virtual system I went to its Scheme. There was alreaady one although I have not done enything to create it/generate it. Then I pressed the "Generate scheme" button and most of the attributes were dublled (see attached picture). The new scheme generation did not add a new attributes.

• Issues with Test button and with tooltip on Generate schema buttons are solved (thanks to Radek).
• Issue with attributes duplicity: We tried it, but we cannot simulate problem (Chrome 56, Chrome 61, Firefox). We need more specific use case, how it simulate. May be is problem on Windows.