-
Title
Which non-alphanumeric characters are valid for password when using PPM? -
Description
Which non-alphanumeric characters are valid for password when using Password Management? -
Resolution
All characters between ASCII 32 and 126 are supported with the exception of " (double quote) and ' (single quote/apostrophe), which TPAM architecture does not allow support of.
TPAM does not allow characters with an ASCII code of 127 or above (i.e., no †‡‰§£, etc.)
The full list of allowed non-alphanumeric characters is:~!@#$%^&*()-+=?/<>|[]{}_ :;.,\`
The (space) character is also allowed.
The above is also detailed in the TPAM System Administration Guide under the section "Password Rules"; and there is also further detail visible form the blue Help Bubbles when generating the Password Rules.
The detailed list from TPAM 2.5.922 System Administration Guide:
(blank space)~ (tilde)` (grave accent)! (exclamation mark)@ (at)# (pound)$ (dollar sign)% (percent)^ (carat)& (ampersand)* (asterisk)( (open parenthesis)) (close parenthesis)_ (underscore)- (hyphen)+ (plus sign)= (equals){ (open brace)} (close brace)[ (open bracket)] (close bracket)| (pipe)\ (backslash): (colon); (semicolon)< (less than), (comma)> (greater than). (period)? (question mark)/ (forward slash)BFER 8979 was submitted as a feature enhancement to consider adding the pound symbol (£) as a supported character for password management.
-
Change Request
8708, 8979 -
Additional Information
In v2.5 there were significant changes to how users authenticate in 2.5. We have confirmed that 2.5.910 and earlier will NOT allow double quotes in passwords even when authenticating to an external source eg. WinAD. BFER 6039 added this feature back with version 2.5.911 and above, and allow double quotes (") in passwords for Local and External Authentications. BFER 6039 "Fixed issue where externally authenticated users were not allowed to have double quotes in their password. Now they can."