Version Affected: All
Overview
Does SecureAuth Identity Platform support passwords that begin or end with a space? This question usually comes up when a password policy allows a space anywhere in a password, and a user whose password begins or ends with a space is told that the password is incorrect when logging in through SecureAuth Identity Platform, even though the password was typed correctly.
Answer
No. SecureAuth Identity Platform does not support a password that begins with a space (a leading space) or ends with a space (a trailing space). A space between other characters in a password is supported.
When a user logs in, SecureAuth Identity Platform removes any leading and trailing spaces from the password that was entered, before it checks the password against the user directory. This is intentional. A leading or trailing space is easily picked up by accident when a password is copied and pasted, and removing it prevents those logins from failing.
As a result, the outcome depends on where the space is in the password:
- A password with a space between other characters, such as Blue Sky42!, is sent to the user directory unchanged and works as expected.
- A password that begins or ends with a space never matches. The space is removed from what the user typed, so the password that reaches the user directory is different from the one stored there, and the login fails with an incorrect password error.
If users log in through SecureAuth Identity Platform, do the following:
- For a user who is already affected, change the password to one that does not begin or end with a space. The user can then log in.
- If the password policy allows a space anywhere in a password, tell users not to begin or end a password with a space, or change the policy so that a leading or trailing space is not allowed.
Which special characters can a password contain?
SecureAuth Identity Platform does not have its own list of allowed special characters. Apart from leading and trailing spaces, it does not add password character restrictions of its own at login. The password is checked by the user directory, so any special character that the user directory and its password policy accept can be used in a password.
For Active Directory, Microsoft lists the following as the special (non-alphanumeric) characters that count toward the Password must meet complexity requirements policy setting:
'-!"#$%&()*,./:;?@[]^_`{|}~+<=>Currency symbols, such as the Euro or British Pound signs, are not counted as special characters by that policy setting. For the full rules, see Microsoft's Password must meet complexity requirements reference. A different user directory, or a custom password filter, can have different rules.
One special character has a known limitation. On versions earlier than 22.12 HF8 and 23.07 HF2, a comma in a password can cause Transparent Single Sign-On (TSSO) to fail when the realm passes the password in a Custom Token or cookie without encrypting or encoding it. Logging in with the password is not affected. Bug: Transparent SSO Fails for Users With a Comma in Their Password describes the fix and the workarounds.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
0 comments
Please sign in to leave a comment.