[midPoint-git] [Evolveum/midpoint] b2d334: Introduce shadow "purpose" property
mederly
noreply at github.com
Fri Oct 6 17:08:37 CEST 2023
Branch: refs/heads/master
Home: https://github.com/Evolveum/midpoint
Commit: b2d33438e75ad49b27aed879d1f49761f9e5c284
https://github.com/Evolveum/midpoint/commit/b2d33438e75ad49b27aed879d1f49761f9e5c284
Author: Pavol Mederly <mederly at evolveum.com>
Date: 2023-10-06 (Fri, 06 Oct 2023)
Changed paths:
M gui/admin-gui/src/main/java/com/evolveum/midpoint/web/page/self/PageAccountActivation.java
M infra/schema/src/main/java/com/evolveum/midpoint/schema/constants/SchemaConstants.java
M infra/schema/src/main/resources/xml/ns/public/common/common-provisioning-3.xsd
M model/model-api/src/main/java/com/evolveum/midpoint/model/api/expr/MidpointFunctions.java
M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/expr/MidpointFunctionsImpl.java
M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/ActivationProcessor.java
M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/password/AbstractPasswordTest.java
M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/password/TestPasswordDefault.java
M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/password/TestPasswordDefaultHashing.java
M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/password/TestPasswordNone.java
R model/model-intest/src/test/resources/password/resource-dummy-lifecycle.xml
A model/model-intest/src/test/resources/password/resource-dummy-purpose.xml
M repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/asserter/ShadowAsserter.java
Log Message:
-----------
Introduce shadow "purpose" property
Some accounts are incomplete in the sense they cannot be used without
some action, like setting up the password. Previously, they were
distinguished by the value of "proposed" in their lifecycleState
property. In the future, however, we plan to bind shadow lifecycle
state to the account lifecycle state as stored on the resource.
This leads to a conflict between these two uses.
We decided to resolve this conflict by introducing special "purpose"
property; and use it to mark these incomplete shadows.
This is an incompatible change. Deployments using the custom lifecycle
state mappings will need to adapt these, as shown in
resource-dummy-purpose.xml file in this commit. Deployments using
account activation feature should activate all pending shadows before
doing the upgrade, or migrate the data manually - by setting
"purpose" property for those pending shadows appropriately.
Commit: 5382a413d73f8a201a7344f80388776f674a7c57
https://github.com/Evolveum/midpoint/commit/5382a413d73f8a201a7344f80388776f674a7c57
Author: Pavol Mederly <mederly at evolveum.com>
Date: 2023-10-06 (Fri, 06 Oct 2023)
Changed paths:
M pom.xml
Log Message:
-----------
Merge remote-tracking branch 'origin/master'
Compare: https://github.com/Evolveum/midpoint/compare/1b52e7b6d5c7...5382a413d73f
More information about the midPoint-svn
mailing list