ActivationType (Complex Type)

Items

• administrativeStatus

  Flags: RAM

  Multiplicity: [0,1]

  This defines the "administrative state", i.e. the administrator's decision. If set, this property overrides any other constraints in the activation type. E.g. if this is set to "enabled" and the object is not yet valid (according to validFrom below), the user should be considered active. If set to "disabled" the user should be considered inactive regardless of other settings. Therefore this property does NOT define an actual state of the object. It is a kind of "manual override". If this property is not present then the other constraints in the activation type should be considered. If not present and there are no other constraints in the activation type or if there is no activation type at all then the values is assumed to be "disabled", i.e. that the described concept is inactive.

• effectiveStatus

  Flags: RAM

  Multiplicity: [0,1]

  This defines the "effective state", i.e. the result of combining several activation settings (administrative status, validity dates, etc.). This holds the result of a computation, therefore it is kind of VIRTUAL property that is recomputed every time. It SHOULD NOT be set directly but it rather should be computed from the values of other activation properties. Therefore it is considered READ ONLY for the high-level code. It may be stored in the repository but in that case it has only an informational value (the effective activation status at the time the object was last updated). If this property is not present then the computation haven't taken place yet.

• validFrom

  Flags: RAM

  Multiplicity: [0,1]

  A date from which is should the object be considered active. Not applied if the "enabled" flag is set to any value.

• validTo

  Flags: RAM

  Multiplicity: [0,1]

  A date to which is should the object be considered active. Not applied if the "enabled" flag is set to any value.

• validityStatus

  Flags: RAM

  Multiplicity: [0,1]

  This property holds the result of vality period computation with respect to the current date and time. E.g. it specifies whether the entity is before the validity period, in the validity perion or after validity period. This holds the result of a computation, therefore it is kind of VIRTUAL property that is recomputed every time. It SHOULD NOT be set directly but it rather should be computed from the values of validity timestamps and current time. Therefore it is considered READ ONLY for the high-level code. It may be stored in the repository but in that case it has only an informational value (the effective activation status at the time the object was last updated). If this property is not present then the computation haven't taken place yet.

• disableReason

  Flags: RAM

  Multiplicity: [0,1]

  URL that identifies a reason for disable. This may be indication that that identity was disabled explicitly, that the disable status was computed or other source of the disabled event.

• disableTimestamp

  Flags: RAM

  Multiplicity: [0,1]

  Timestamp of last modification of the activation status to the disabled state. Note: This timestamp is used for recording purposes. Changing it will NOT change the activation state.

• enableTimestamp

  Flags: RAM

  Multiplicity: [0,1]

  Timestamp of last modification of the activation status to the enabled state. Note: This timestamp is used for recording purposes. Changing it will NOT change the activation state.

• archiveTimestamp

  Flags: RAM

  Multiplicity: [0,1]

  Timestamp of last modification of the activation status to the archived state. Note: This timestamp is used for recording purposes. Changing it will NOT change the activation state.

• validityChangeTimestamp

  Flags: RAM

  Multiplicity: [0,1]

  Timestamp of last modification of the effective validity state, i.e. last time the validity state was recomputed with result that was different than the previous recomputation. It is used to avoid repreated validity change deltas. Note: This timestamp is used for recording purposes. Changing it will NOT change the activation state.

• lockoutStatus

  Flags: RAM

  Multiplicity: [0,1]

  This defines the state of user or account lock-out. Lock-out means that the account was temporarily disabled due to failed login attempts or a similar abuse attempt. This value is usualy set by the resource (or midpoint internal authentication code). It is unlikely that it can be set to the "locked" value. However it usually can be used to unlock the account by setting this property to "normal" value.

• lockoutExpirationTimestamp

  Flags: RAM

  Multiplicity: [0,1]

  Timestamp of a moment when account lockout expires and the account will be normally usable again. This is only an informational value. It should be considered as read-only for most cases. It only makes sense if the lockoutStatus is not in the "normal" state.