Task #539
closed
Inactive system fills provisioning queue
Added by Marcel Poul over 7 years ago.
Updated over 5 years ago.
Description
When system is inactive, it still fills the provisioning queue. It is known behaviour, but in common usecases, you won't use it.
Much better would be following behaviour:
Inactive system will do Account management for preparing account with uid, other attribute transformation for provisioning will not executed, as well as no operation fill the provisioning queue.
This feature we would use pretty often - e.g. during system synchronization (other systems set as inactive).
- Subject changed from Active system fills provisioning queue to Inactive system fills provisioning queue
- Assignee changed from Ondřej Kopr to Radek Tomiška
- Category changed from Feedback to Provisioning
We discussed this with Petr Fiser and find one possible usecase for the current behaviour of inactive system: When there is some malfunction of stoppage of managed system that has loooong timeouts , we would use inactive checkbox to prevent all communication with it. But this usecase is so rare that I do not believe, we would ever come across it.
- Priority changed from Normal to Low
- Target version set to Diamond (7.4.0)
This was the main requirement to inactive system - even read operations cannot be executed, because target system is offline (e.g. for maintenance reason).
- Target version deleted (
Diamond (7.4.0))
- Status changed from New to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- Target version set to Quartz (9.6.0)
- % Done changed from 0 to 90
I implemented new feature - disabled provisioning on the system. Is the new configuration property on the system detail. System with disabled provisioning doesn't put an operation into queue - just ACM is called and IdM account with uid attribute is created only. System with disabled provisioning is not available for a password change.
Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/715c6fab2699b05d2fe692c2f3ee844bd98dcb0a
Note: Disabled (~inactive) system behavior is leaved unchanged (~offline system).
Documentation remains.
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Radek Tomiška
- Priority changed from Low to Normal
- % Done changed from 90 to 100
I made review, it works perfectly, thanks for that.
- Status changed from Resolved to Closed
- Description updated (diff)
- Related to Feature #1655: Enable synchronization for the system marked as inactive with provisioning queue added
- Related to Defect #1859: Password on target system cannot be changed until the first provisioning occurs added
- Related to Defect #2433: Password change failed for accounts without system entity added
Also available in: Atom
PDF
