Defect #1553: Limit equals in provisioning brake - IdStory Identity Manager

Actions

Copy link

Defect #1553

closed

Task #1503: Testing of the product (9.4.0)

Limit equals in provisioning brake

Added by milus kotisova almost 6 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Low

Assignee:

Ondřej Kopr

Category:

Provisioning

Target version:

Quartz (9.6.0)

Start date:

03/14/2019

Due date:

% Done:

100%

Estimated time:

Affected versions:

Owner:

Description

@affected version 9.4.0

Deletion provisioning brake setup:
period - 1 min
warning limit - 2 records
deletion blocking limit - 2 records
44 record were processed.

The case is described in detail in https://redmine.bcvsolutions.eu/issues/17578.
Records blocked in IdM but clearly deleted in AD.

Here, the product-related issue is merely that the message wrongly informs that a limit of 3 records has been exceeded. A fourth record is then blocked,
not the 3rd one as one might expect.

And as for the column titled Processed operations (in screenshot 4_operace), what does the wording Number of processed operations (4) mean in this particular case? What kind of operations are counted?

Files

Download all files

brake_setup.png (72 KB) brake_setup.png		milus kotisova, 03/14/2019 03:37 PM
4_operace.png (30.2 KB) 4_operace.png		milus kotisova, 03/14/2019 03:37 PM
notifikace.png (34.6 KB) notifikace.png		milus kotisova, 03/14/2019 03:37 PM
log_HB (21 KB) log_HB		milus kotisova, 03/14/2019 03:45 PM

Actions

Copy link

Updated by Radek Tomiška almost 6 years ago

Assignee changed from Radek Tomiška to Ondřej Kopr

Actions

Copy link

Updated by Radek Tomiška almost 6 years ago

Tracker changed from Defect to Feature
Priority changed from Normal to Low

I think the behavior is ok, but message can be improved to prevent misunderstanding.

Actions

Copy link

Updated by Alena Peterová almost 6 years ago

I tested this on 9.3.4 and there must be some bug - when the brake has disable limit 2 and it allows to delete 3 accounts, it's not only wrong message, but also wrong behavior.

Actions

Copy link

Updated by Alena Peterová almost 6 years ago

Alena Peterová wrote:

I tested this on 9.3.4 and there must be some bug - when the brake has disable limit 2 and it allows to delete 3 accounts, it's not only wrong message, but also wrong behavior.

I tested it repeatedly by bulk role removing and it happened in about 50 % cases. Maybe there is some problem with asynchronous processing?

Actions

Copy link

Updated by Radek Tomiška almost 6 years ago

Alena Peterová wrote:

I tested this on 9.3.4 and there must be some bug - when the brake has disable limit 2 and it allows to delete 3 accounts, it's not only wrong message, but also wrong behavior.

Agree, we will look at it (we didn't understand a ticket description at first "Incorrect provisioning brake message" ...).

Actions

Copy link

Updated by Ondřej Kopr almost 6 years ago

Status changed from New to In Progress
Target version set to Quartz (9.6.0)

Actions

Copy link

Updated by Ondřej Kopr almost 6 years ago

Tracker changed from Feature to Defect
Subject changed from Incorrect provisioning brake message to Limit equals in provisioning brake
Status changed from In Progress to Needs feedback
Assignee changed from Ondřej Kopr to milus kotisova
% Done changed from 0 to 90

I checked your settings of provisioning brake and the settings:

warning limit 2
disable limit 2

This settings worked with this algorithm:

first check the warning
then check disable

For this settings is for second provisioning operation checked first warning and then continue with provisioning operation. For third provisioning operation run was finally checked the disable. So the 4 operation was blocked. I updated the behavior with evaluation warning and disable check, now is first checked disable and then warning check.

Only information for this settings: for your case will not be sent the warning message, because is same as disable check.

The issue that describe Alca I try debugging and test with different idm settings (asynchronous provisioning on/off, event process asynchronous on/off), but for local environment it is working correctly.

So for better sleeping and rest in soul I moved whole method with check the counter for provisioning brake into synchronized method.

Commit: https://github.com/bcvsolutions/CzechIdMng/commit/5ef5d5ae23ce0ca2e6d55d646ac41b873374f70d (branch develop)

Information with equals or higher limits was added into documentation:
https://wiki.czechidm.com/devel/documentation/provisioning/dev/break
https://wiki.czechidm.com/tutorial/adm/create_provisioning_break#create_the_provisioning_brake_configuration

Please Milus could you check yout scenarios again? Now it is working better with equals limits. Thank you.

Actions

Copy link