User IDs and passwords

The character limitations provided here apply to the WebSphere Portal administrator, IBM WAS administrator, database administrator, LDAP server administrator, and user IDs. Your company may have more restrictive user ID and password requirements.

Regardless of what characters we can enter on the user information form, user ID and passwords are limited to the valid characters described here.

WebSphere Portal cannot create user IDs or passwords containing spaces, although it fully supports any existing user IDs and passwords or those created in the user repository containing spaces.

Under normal circumstances a valid user ID and password can contain the following characters:

• Lowercase characters {a-z}
• Uppercase characters {A-Z}
• Numbers {0-9}
• Exclamation point {!}
• Open parenthesis {(}
• Close parenthesis {)}
• Dash {-}; Not supported as the first character.
• Period {.}; Not supported as the first character.
• Underscore {_}; this is the only supported special character in IBM i
• Grave accent {`}
• Tilde {~}
• Commercial at {@}

Non-ASCII characters are not allowed for username or password.

(Linux only) 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

...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.

(Windows only) 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

...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"

Parent: Plan
Related:
Portal configuration services