Project

General

Profile

Actions
Copy link

Task #866

open

Create system entity only after successful create

Added by Alena Peterová about 7 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Vít Švanda
Category:
Account managment
Target version:
-
Start date:
12/06/2017
Due date:
% Done:

0%

Estimated time:
Owner:

Description

Version 7.6.0
Affects any system that generates its own identifier (e.g. AD - objectGUID)
I add the role "AD" to the identity and the provisioning fails. But the not-created account is listed in the "Entities in system" with the identifier that was generated by IdM. This seems to be a bug, because there definitely isn't any account with such identifier on the real system.

Actions
Copy link
 #1

Updated by Vít Švanda about 7 years ago

It is true. Provisionig queue now works and needs the SystemEntity. This is the reason, why SystemEntity is created, when provisioning starts (SystemEntity is created with attribute wish=true). After successed connector call is SystemEntity.UID (by UID from the connector) updated and attribute SystemEntity.wish is set to false.
When connector call fails, then SystemEntity has still "wish" attribute = true.

This is now a standard behavior.

Actions
Copy link

Also available in: Atom PDF