Common use of User Authentication Clause in Contracts

User Authentication. 6.2.6.1 Users will usually be authenticated by use of a password. Strong authentication methods (e.g. one-time passwords, digital signatures, etc.) may be required in the future. 6.2.6.2 Passwords must not be stored in script files. 6.2.6.3 Passwords must be entered by the user in real time. 6.2.6.4 Passwords must be at least six to eight (6-8) characters in length, not blank or a repeat of the userid; contain at least one letter, and at least one number or special character must be in a position other than the first or last one. This format will ensure that the password is hard to guess. Most systems are capable of being configured to automatically enforce these requirements. Where a system does not mechanically require this format, the users must manually follow the format. 6.2.6.5 Systems will require users to change their passwords regularly (usually every thirty-one (31) days). 6.2.6.6 Systems are to be configured to prevent users from reusing the same password for six (6) changes/months. 6.2.6.7 Personal passwords must not be shared. A user who has shared his password is responsible for any use made of the password.

Appears in 11 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

User Authentication. 6.2.6.1 Users will usually be authenticated authe nticated by use of a password. Strong authentication methods (e.g. one-time passwords, digital signatures, etc.) may be required in the future. 6.2.6.2 Passwords must not be stored in script files. 6.2.6.3 Passwords must be entered by the user in real time. 6.2.6.4 Passwords must be at least six to eight (6-8) characters in length, not blank or a repeat of the userid; contain at least one letter, and at least one number or special character must be in a position other than the first or last one. This format will ensure that the password is hard to guess. Most systems are capable of being configured to automatically enforce these requirements. Where a system does not mechanically require this format, the users must manually follow the format. 6.2.6.5 Systems will require users to change their passwords regularly (usually every thirty-one (31) days). 6.2.6.6 Systems are to be configured to prevent users from reusing the same password for six (6) changes/months. 6.2.6.7 Personal passwords must not be shared. A user who has shared his password is responsible for any use made of the password.

Appears in 1 contract

Samples: Interconnection Agreement

AutoNDA by SimpleDocs

User Authentication. 6.2.6.1 7.8.1 Users will usually be authenticated by use of a password. Strong authentication methods (e.g. one-time passwords, digital signatures, etc.) may be required in the future. 6.2.6.2 7.8.2 Passwords must not be stored in script files. 6.2.6.3 7.8.3 Passwords must be entered by the user in real timeuser. 6.2.6.4 7.8.4 Passwords must be at least six (6) to eight (6-8) characters in length, not blank or a repeat of the useriduser ID; contain at least one (1) letter, and at least one (1) number or special character must be in a position other than the first or last one. This format will ensure that the password is hard to guess. Most systems are capable of being configured to automatically enforce these requirements. Where a system does not mechanically require this format, the users must manually follow the format. 6.2.6.5 7.8.5 Systems will require users to change their passwords regularly (usually every thirty-one (31) days). 6.2.6.6 7.8.6 Systems are to be configured to prevent users from reusing the same password for six (6) changes/months. 6.2.6.7 7.8.7 Personal passwords must not be shared. A user who has shared his password is responsible for any use made of the password.

Appears in 1 contract

Samples: Two Way CMRS Interconnection Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!