Temporary block of activation

[romanstrobl]

Description

As of now, the activation becomes blocked after reaching the configured max attempts.

We want to remove the block after a configured time period.
The feature should apply for cryptography protocol v4 (and higher).

• The block period is configurable, default 5 minutes.
• To prevent brute forcing, in case of consecutive blocking, the block period is multiplied by a configurable multiplier (default 2). i.e., defaulst 1st block period is 5 minutes, second 10 minutes, third 20 minutes, and so on.
• The timestamp when the block would be lifted is at disposal in SDK (activation status response).
• After the block period ends, the activation status is set to ACTIVE, unless the activation was removed.
• The effect of unblocking should be immediate - at least in case a user tries to use the activation.
• The effect of unlocking should NOT reset the fail attempt counter., e.g., 6th consecutive incorrect attempt blocks the device for a prolonged period, but the activation should be usable after unblocking.
• The successful attempt currently resets the fail attempt counter, this attempt should also reset the multiplier for the block period.
• The operation status is independent from the activation status i.e., operations fail when their max attempts is reached.

Acceptance criteria

The activation blocks after reaching the max attempts, but is eventually unblocked.

Technical specification

The basic activation status enum should not be expanded - a temporarily blocked activation should behave as a blocked activation.

The temporary block feature is configurable.
The block period is configurable.
The multiplier for extending the block period is configurable.

QA specification

Tested manually because of timeouts.