syst_owner_password_rules

The record’s primary key. The definitive identifier of the record in the system.

General Usage

This column is system maintained and should be considered read only in normal operations.

Defines the relationship with the specific Owner for whom the password rule is being defined.

An integer range of acceptable password lengths with the lower bound representing the minimum length and the upper bound representing the maximum password length.

General Usage

A zero or negative value on either bound indicates that the bound check is disabled. Note that disabling a bound may still result in a bounds check using the application defined default for the bound.

Length is determined on a per character basis, not a per byte basis.

An interval indicating the maximum allowed age of a password. Any password older than this interval will typically result in the user being forced to update their password prior to being allowed access to other functionality. The specific user workflow will depend on the implementation details of application.

General Usage

An interval of 0 time disables the check and passwords may be of any age.

Establishes the minimum number of upper case characters that are required to be present in the password.

General Usage

Setting this value to 0 disables the requirement for upper case characters.

Setting this value to 0 disables the requirement for lower case characters.

Establishes the minimum number of numeric characters that are required to be present in the password.

General Usage

Setting this value to 0 disables the requirement for numeric characters.

Establishes the minimum number of non-alphanumeric characters that are required to be present in the password.

General Usage

Setting this value to 0 disables the requirement for non-alphanumeric characters.

When passwords are changed, this value determines how many prior passwords should be checked in order to prevent password re-use.

General Usage

Setting this value to zero or a negative number will disable the recently used password check.

When true new passwords submitted through the change password process will be checked against a list of common passwords and passwords known to have been compromised and disallow their use as password credentials in the system.

General Usage

When false submitted passwords are not checked as being common or against known compromised passwords; such passwords would therefore be usable in the system.

When true, an approved multi-factor authentication method must be used in addition to the password credential.

A array of the approved multi-factor authentication methods.

The database server date/time when the transaction which created the record started.

General Usage

This column is system maintained and should be considered read only in normal operations.

The database role which created the record.

General Usage

This column is system maintained and should be considered read only in normal operations.

The database server date/time when the transaction which modified the record started. This field will be the same as diag_timestamp_created for inserted records.

General Usage

This column is system maintained and should be considered read only in normal operations.

The database server date/time at the moment the record was actually modified. For long running transactions this time may be significantly later than the value of diag_timestamp_modified.

General Usage

This column is system maintained and should be considered read only in normal operations.

The database role which modified the record.

General Usage

This column is system maintained and should be considered read only in normal operations.

The current version of the row. The value here indicates how many actual data changes have been made to the row. If an update of the row leaves all data fields the same, disregarding the updates to the diag_* columns, the row version is not updated, nor are any updates made to the other diag_* columns other than diag_update_count.

General Usage

This column is system maintained and should be considered read only in normal operations.

Direct Usage

This column is frequently used by by application logic to resolve the “dirty write” issues which can arise from concurrent data changes. As such any administrative override of automatic system maintenance of this value should consider the ramifications on application function.

Records the number of times the record has been updated regardless as to if the update actually changed any data. In this way needless or redundant record updates can be found. This row starts at 0 and therefore may be the same as the diag_row_version - 1.

General Usage

This column is system maintained and should be considered read only in normal operations.