Feature #3348
closedImplement account management for technical acounts
100%
Description
Parts of the account management are already implemented, such as TechnicalAccountProvisioningExecutor, but AccountManagementService, and some processors still rely on identity provisioning and cannot handle other types of account owners. This results in some weird issues, such as provisioning not being invoked when new roles are assigned to technical accounts and so on.
The goal of this ticket is to clean up the rough parts of technical account provisioning and account management and implement missing stuff.
Updated by Peter Štrunc about 1 year ago
- Target version changed from 1.0.2 to 1.1.0
Updated by Peter Štrunc about 1 year ago
- Sprint set to Sprint 13.0.5 - 1 (May 03 - May 17)
Updated by David Štekl about 1 year ago
- Status changed from In Progress to Resolved
Updated by David Štekl about 1 year ago
- Status changed from Resolved to In Progress
Updated by Peter Štrunc almost 1 year ago
- Sprint changed from Sprint 13.0.5 - 1 (May 03 - May 17) to Sprint 13.0.5 - 2 (May 17 - May 29)
Updated by Peter Štrunc 12 months ago
- Status changed from In Progress to Needs feedback
- Assignee changed from Peter Štrunc to Ondřej Kopr
- % Done changed from 70 to 80
- Owner set to Peter Štrunc
https://github.com/bcvsolutions/technical-accounts/pull/2
https://github.com/bcvsolutions/CzechIdMng/pull/393
@kopro could you check it out?
Updated by Ondřej Kopr 12 months ago
- Status changed from Needs feedback to Resolved
- Assignee changed from Ondřej Kopr to Peter Štrunc
- % Done changed from 80 to 100
I made code review - LGTM! Thanks for abstraction service a processors.
I just found one thing that is probably only about understanding the code.
Processors AbstractRoleAssignmentDeleteAccountProcessor has order -900 (before delete). Original processor for identity role (IdentityRoleDeleteAccountProcessor) had -1000 did you want order -900, 100 or original -1000.
It is just minor thing, or question.
Otherwise everything else looks good!