I wanted to find out for sure if what I experienced today with a password is a standard error or if something else is going on.
For a new user account the password was set with some alpha characters, a number and an "@"
The user could not log into the database from either application that was the reason for the user.
When the "@" was replaced in the password with another character the user could log in through both apps.
According to books online [see below] there are certain special characters listed that specifically cannot be used and there are examples of special characters that can be used. .... but the "@" sign is not listed in either set of characters.
So, my question is, would this be an application password limitation or a SQL Server login limitation?
Thank you for your insight!
FROM BOOKS ONLINE
Password complexity policies are designed to deter brute force attacks by increasing the number of possible passwords. When password complexity policy is enforced, new passwords must meet the following guidelines:
•The password does not contain all or part of the account name of the user. Part of an account name is defined as three or more consecutive alphanumeric characters delimited on both ends by white space such as space, tab, and return, or any of the following characters: comma (,), period (.), hyphen (-), underscore (_), or number sign (#).
•The password is at least eight characters long.
•The password contains characters from three of the following four categories:
◦Latin uppercase letters (A through Z)
◦Latin lowercase letters (a through z)
◦Base 10 digits (0 through 9)
◦Non-alphanumeric characters such as: exclamation point (!), dollar sign ($), number sign (#), or percent (%).
Passwords can be up to 128 characters long. You should use passwords that are as long and complex as possible.