□
□ □
□ | □
It 's my understanding that the protocol should be authentication-type agnostic , and therefor whatever is being sent should be encrypted as a whole , irrespective of if it 's a username , password , private key , or whatever . You should avoid using an initial password that is a function of the username , is part of the user 's name , or some algorithmically generated password that can easily be guessed . In order to use these forums , users are required to provide a username , password and e-mail address . Once you have done this , you can log into LSE for You using your alumni e mail address as the username , which needs to be typed out in full e.g . The second type is a socks4 / 5 or http proxy firewall that requires a username , password , etc. The GSS_Import_name ( ) operation resolves this uid into a username , which is then treated as the User Name Form . The EXTERNAL mechanism just states the username , and the server uses some implicit context to authenticate it . Be sure that you aren ’ t appending " oswego.edu " to the username , or supplying your full name instead of a username . To change the username , you must delete the existing user and create a new one using the new name .