Characters that are valid for user IDs and passwords
Understanding character limitations for user IDs and passwords is important because they are used throughout WebSphere Application Server to provide access and secure content. The character limitations provided here apply to the WebSphere Application Server administrator, the database administrator, the LDAP server administrator, and user IDs. Database and LDAP servers can have more restrictive limitations than provided here. Therefore you should check the database and LDAP server product documentation for restrictions. Failure to correctly define user IDs and passwords during the installation process can result in installation failure. In addition, your specific installation might have more restrictive user ID and password requirements that you must also follow.
避免困難: WebSphere Application Sever cannot create user IDs or
passwords that contain spaces, although it fully supports any existing
user IDs and passwords or those created in the user repository that
contain spaces.gotcha
Note: The only
supported characters in IBM i are lowercase characters, uppercase
characters, numbers, and the underscore.- Lowercase characters {a-z}
- Uppercase characters {A-Z}
- Numbers {0-9}
- Exclamation point {!}
- Open parenthesis {(}
- Close parenthesis {)}
- Dash {-}; this character is not supported as the first character in the user ID or password
- Period {.}; this character is not supported as the first character in the user ID or password
- Question mark {?}
- Open bracket {[}
- Close bracket {]}
- Underscore {_}; this is the only supported special character in IBM i
- Grave accent {`}
- Tilde {~}
- Commercial at {@}, this character is not supported when creating the WebSphere Application Server administrator during installation.
- Hash mark (or pound sign) {#}
- Single {'} and double {"} quotation marks - Although these two characters are supported, using both in a single user ID is not supported. Ensure that you are not using both the characters in a single user ID.
避免困難: These are all ASCII characters.
Non-ASCII characters are not allowed for a username or password.gotchaIf you plan on using a non-ASCII based encoding, ensure your Java Virtual Machine has the correct generic arguments specific for the non-ASCII based encoding. For example, for UTF-8 encoding, the following two parameters should be added to the Java Virtual Machine generic arguments for WebSphere Portal: -Dfile.encoding=UTF-8 and -Dclient.encoding.override=UTF-8.
Note: Some tasks might require you to enter the
fully qualified user ID. If your fully qualified user ID contains
a space; for example: cn=wpsadmin,cn=users,l=SharedLDAP,c=US,ou=Lotus,o=Software
Group,dc=ibm,dc=com, you must place the fully qualified
user ID in the properties file or into a parent properties file instead
of as a flag on the command line. For example, create a parent properties
file called mysecurity.properties, enter the
fully qualified user ID, and then run the task: ./ConfigEngine.sh task_name -DparentProperties=/opt/mysecurity.properties.
Note: Some tasks may require you to enter the fully qualified
user ID. If your fully qualified user ID contains a space; for example: cn=wpsadmin,cn=users,l=SharedLDAP,c=US,ou=Lotus,o=Software
Group,dc=ibm,dc=com, you must place quotes around the
fully qualified user ID before running the task; for example, "cn=wpsadmin,cn=users,l=SharedLDAP,c=US,ou=Lotus,o=Software
Group,dc=ibm,dc=com".The following table contains a list of the required fields on the user information form and the supported characters.
| User information | Valid characters | Unsupported characters |
|---|---|---|
| User ID | Note: The only supported characters in IBM i are lowercase characters, uppercase
characters, numbers, and the underscore.
|
Only ASCII characters are allowed. Other restrictions: The user ID cannot contain
spaces; for example, user name.
If
you enter any unsupported characters during the installation, you
will receive an error message that states which character is invalid.
For example, "The special character [@] was found in the administrative
user ID field. Enter the administrative user ID again."
避免困難: You receive a different error message
if you enter any unsupported characters when creating users through
the Manage users and groups portlet.gotcha |
| Password / Confirm password | Note: The only supported characters in IBM i are lowercase characters, uppercase
characters, numbers, and the underscore.
|
Diacritics, such as the umlaut, and DBCS characters are not allowed. Other restrictions: The
password cannot contain spaces; for example, pass
word.
避免困難: Login or ConfigEngine tasks might
fail if the password contains any unsupported characters, including
DBCS characters. This action happens even if a user is successfully
enrolled using a password containing DBCS characters.gotchaIf you enter any unsupported characters during the installation, you will receive an error message that states which character is invalid. For example, "The special character [@] was found in the password field. Enter the password again." |
| First Name | All characters | n/a |
| Last Name | All characters | n/a |
The previous characters are true if the user.UNIQUEID.charset parameter is set to ascii. If set to unicode, the standard Java™ Letter definition is used and all characters that are recognized as letter or digit by Java are allowed by default. See the Puma Validation Service section in the Portal configuration services link for information about further parameters that can be modified to affect the behavior of Portal's validation of users, groups, and passwords.
![[AIX]](../images/aixlogo.gif)
![[Solaris]](../images/solaris.gif)
概念主題