ResourceActivationDefinitionType (Complex Type)

Items

• existence

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 80

  Mapping for resource object existence. This mapping decides whether the resource object should exist at all.

• administrativeStatus

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 10

  Mapping for activation administrative status.

• validFrom

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 50

  Mapping for activation start of validity.

• validTo

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 60

  Mapping for activation end of validity.

• lockoutStatus

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 70

  Mapping for activation lockout status.

• disableInsteadOfDelete

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 20

  If an account is unassigned and there is no other existing assignment for an account midPoint will de-provisioning that account. Which means that the account will be deleted. This is the default behavior. But it can be changed. This configuration change default behavior and account will be disabled instead delete.

• delayedDelete

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 30

  If an account is unassigned and there is no other existing assignment for an account midPoint will de-provisioning that account. Which means that the account will be deleted. This is the default behavior. But it can be changed. This configuration change default behavior and account will delete with delay and meanwhile account will be disabled. We use activation/disableTimestamp from shadow object as reference attribute. As disable reason we use de-provision or mapped.

• preProvision

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Display order: 40

  This configuration will pre-provision a disabled account defined time before focus’s activation/validFrom date.