[Date Prev][Date Next] [Chronological] [Thread] [Top]

userPassword Octet String


attributetype ( NAME 'userPassword'
        EQUALITY octetStringMatch
        SYNTAX{128} )

How should a client behave when the user types in a password with
NON-ASCII characters? Very likely you receive the password in some
type of character set/encoding within your system environment.

Personally I encode the user input as UTF-8 before setting the
userPassword attribute or doing a bind. But according to the schema
definition above this might be wrong. But if there's no rule how to
encode user's input every LDAP client would be free to store any
password value leading to incompatible password handling. Or did I
misunderstand something?

Ciao, Michael.