Project

General

Profile

Actions

Defect #1315

closed

Delete of identity doesn't create virtual system request

Added by Vladimír Kotýnek over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Vít Švanda
Category:
Virtual systems
Target version:
-
Start date:
10/11/2018
Due date:
% Done:

0%

Estimated time:
Affected versions:
Owner:

Description

Affected version: 9.2
Use-case:
  1. Create virtual system - check that the "Required confirmation by the implementer" checkbox in configuration!
  2. Create user (e.g. jdoe)
  3. Create CSV to import users (jdoe) into virtual system
  4. Import CSV
  5. Run Synchronization of the virtual system
  6. Check whether the user account on virtual system is linked to the identity (jdoe)
  7. Check whether the identity has role
  8. Go to "Users" list, find jdoe and select by clicking checkbox in the left column
  9. Delete jdoe
  10. Wait for the end of the operation - no errors
  11. Check tasks on the system - no task to delete "jdoe" account, jdoe is in "entities on system" and not in accAccounts

I didn't tested delete operation when identity is removed for non-virtual systems.
I would expect "delete" request to be created when the identity is deleted.


Files


Related issues

Related to IdStory Identity Manager - Defect #1326: Virtual systems - default role is wrong mapped on SYNC mappingClosedVít Švanda10/16/2018

Actions
Actions #1

Updated by Vít Švanda over 5 years ago

I tried it and creation of a request (on identity delete) works for me correctly.

Did you check provisioning queue and event queue on some error?
If you try to assign the "VS role" to some identity, will an account and VS request be created?

Actions #2

Updated by Vladimír Kotýnek over 5 years ago

Yes I've checked the provisioning queue and it was empty. I also checked provisioning archive and there were only those two records created by import. Even in Entity Events there were no errors.
I've tried to assign the role to a different user and the request was created. Then I confirmed the request, everything was OK. Then I removed the role from the user and the request was also created.
Did you tested the scenario on an account imported via Import entities to the system feature (#1286)?

Actions #3

Updated by Vít Švanda over 5 years ago

No, I tested creation of the VS account only by assign the role. Import to system is not in the product now.
- Can you add the CSV file with "broken" user?

Actions #4

Updated by Vladimír Kotýnek over 5 years ago

I uset this CSV:

"username";"email";"firstName";"lastName";"phone";"titleAfter";"titleBefore";"__ENABLE__" 
"jdoe";"jdoe@somename.com";"John";"Doe";"";"bc.";"";"false" 

I've created identity John Doe (login jdoe) (only login, name, surname, e-mail, phone and default contract set as external, nothing else) in IDM before the import and synchronization.

Actions #5

Updated by Vít Švanda over 5 years ago

  • Related to Defect #1326: Virtual systems - default role is wrong mapped on SYNC mapping added
Actions #6

Updated by Vít Švanda over 5 years ago

  • Status changed from Needs feedback to In Progress
  • Assignee changed from Vladimír Kotýnek to Marek Klement

Marku, please check this issue.

Actions #7

Updated by Marek Klement over 5 years ago

  • Assignee changed from Marek Klement to Vít Švanda
  • After Vitek fixed issue #1326 I checked if after deleting of identity it will create request.
  • I checked it on my branch where I developed import and even with import it creates request.
  • Exactly what I did:
    1) Generated virtual system
    2) imported test file where user Kopr was also
    3) Start prepared synchronization on my VS
    4) Then I deleted user Kopr from IdM
    5) The request was generated for me
  • Also tried to delete an account on VS and it did create request as well.

I think that Vitek fixed this issue.

Actions #8

Updated by Vladimír Kotýnek over 5 years ago

I also checked several scenarios of creating VS, importitng user and deleting it's identity today. Testing was performed on the same version (exactly the same CzechIdM only custom a module was updated since the last testing) as before. Request was always created. You may close this ticket, if the bug occures again we can reopen it.

Actions #9

Updated by Vít Švanda over 5 years ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF