Neoview ODBC Drivers Manual (R2.5)

Passwords for platform-level users are encrypted in transit in the same way as LDAP user
passwords and are stored on the Neoview platform in an encrypted form.
Passwords for platform-level users have the following characteristics:
• Minimum length of 8 bytes
• Maximum length of 64 bytes
NOTE: If you use 1024-bit keys, the combined length of the passwords for a platform user
ID and cannot exceed 70 characters.
• Must contain at least one of each of the following: uppercase character, lowercase character,
digit, non- alphanumeric character
• May not contain double-quotes (“), semi-colons (;), forward slashes (/), or commas (,).
• May not contain the user's name
• May not contain more than two consecutive instances of the same character
• May contain blanks but may not begin or end with a blank
• May contain non-printable ASCII characters
• May not contain non-ASCII characters
• Do not expire unless you modify the security policy to specify expiration
After three failed attempts at logging on, a platform user has to wait for 30 seconds before retrying.
Passwords for Database (LDAP) Users
Passwords for LDAP users must match those defined in the external directory. LDAP password
administration is performed in the LDAP server environment, except that:
• You can configure the Neoview platform to notify you when your password will soon expire.
• You can change your LDAP password, using the NCI ALTER PASSWORD command
described in the Neoview User Management and Security Administration Guide, provided that
the grace count configured on the LDAP server has not been exhausted.
NOTE: The Neoview platform does not provide means for a customer ODBC application to
change the password of an LDAP user. If you attempt to use ODBC connection attributes to
change the password of an LDAP user, the ODBC client reports an error.
Use of Braces in Passwords
Certain ODBC applications—notably those which use the .NET ConnectionStringBuilder
class—add braces as delimiters around a password that contains special characters. For example,
the password you enter as ab12_WV is delimited by the .NET framework to become {ab12_WV}.
To compensate for this behavior, the Neoview ODBC driver strips off the delimiting braces.
Suppose, however, that you want to delimit a password with braces or to include a brace within
a password. To allow for such choices, an application that specifies a password in the connection
string must follow these rules:
• To permit a password to include braces as its first and last characters, you must add an extra
left brace at the beginning and an extra right brace at the end.
• To permit a right brace anywhere within the password, you must add an extra right brace
before it as an escape character.
• A left brace within a password, other than as the first character, requires no special handling.
The following examples illustrate these rules. Notice that in the first case, there are actually three
right braces: the first is an escape character, the second is the brace that will remain part of the
20 HP Neoview ODBC Driver Overview for Windows